Skip to content
This repository has been archived by the owner on Feb 23, 2024. It is now read-only.

All Products: <select> looks different in the editor vs frontend #2506

Closed
Aljullu opened this issue May 19, 2020 · 11 comments
Closed

All Products: <select> looks different in the editor vs frontend #2506

Aljullu opened this issue May 19, 2020 · 11 comments
Assignees
@tarunvijwani
Labels
block: all products Issues related to the all products block. focus: global styles Issues that involve styles/css/layout structure. status: on hold The issue is currently not prioritized or is awaiting something (for example, a fix upsteam). status: stale Stale issues and PRs have had no updates for 60 days. type: good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team.

Comments

@Aljullu
Copy link
Contributor

Aljullu commented May 19, 2020

Several blocks, like All Products, have native <select> elements that inherit some styles in the editor (via the selector .wp-core-ui select). Those styles are not loaded in the frontend so they look different editor vs frontend.

Screenshots
Editor:
imatge

Frontend:
imatge

Note: this issue is not about the <select> being disabled (see #2487), but about it having different padding, background, border, etc.
@nerrad nerrad added the block: all products Issues related to the all products block. label Jun 7, 2020
@github-actions
Copy link
Contributor

This issue has been marked as stale because it has not seen any activity within the past 60 days. Remove the stale label or post a comment, otherwise it will be closed in 10 days.

@github-actions github-actions bot added the status: stale Stale issues and PRs have had no updates for 60 days. label Dec 16, 2020
@nerrad nerrad removed the status: stale Stale issues and PRs have had no updates for 60 days. label Dec 16, 2020
@github-actions
Copy link
Contributor

This issue has been marked as stale because it has not seen any activity within the past 60 days. Our team uses this tool to help surface issues for review. If you are the author of the issue there's no need to comment as it will be looked at.

Internal: After 10 days with no activity this issue will be automatically be closed.

@github-actions github-actions bot added the status: stale Stale issues and PRs have had no updates for 60 days. label Feb 15, 2021
@nerrad nerrad added type: good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. focus: global styles Issues that involve styles/css/layout structure. and removed status: stale Stale issues and PRs have had no updates for 60 days. labels Feb 16, 2021
@github-actions
Copy link
Contributor

This issue has been marked as stale because it has not seen any activity within the past 60 days. Our team uses this tool to help surface issues for review. If you are the author of the issue there's no need to comment as it will be looked at.

Internal: After 10 days with no activity this issue will be automatically be closed.

@github-actions github-actions bot added the status: stale Stale issues and PRs have had no updates for 60 days. label Apr 19, 2021
@nerrad nerrad removed the status: stale Stale issues and PRs have had no updates for 60 days. label Apr 21, 2021
@github-actions
Copy link
Contributor

This issue has been marked as stale because it has not seen any activity within the past 60 days. Our team uses this tool to help surface issues for review. If you are the author of the issue there's no need to comment as it will be looked at.

Internal: After 10 days with no activity this issue will be automatically be closed.

@github-actions github-actions bot added the status: stale Stale issues and PRs have had no updates for 60 days. label Jun 21, 2021
@nerrad nerrad removed the status: stale Stale issues and PRs have had no updates for 60 days. label Jun 25, 2021
@github-actions
Copy link
Contributor

This issue has been marked as stale because it has not seen any activity within the past 60 days. Our team uses this tool to help surface issues for review. If you are the author of the issue there's no need to comment as it will be looked at.

Internal: After 10 days with no activity this issue will be automatically be closed.

@github-actions github-actions bot added the status: stale Stale issues and PRs have had no updates for 60 days. label Aug 25, 2021
@nerrad nerrad removed the status: stale Stale issues and PRs have had no updates for 60 days. label Aug 26, 2021
@nerrad
Copy link
Contributor

nerrad commented Aug 26, 2021

Just tested this today and the issue still exists (tested Storefront).

@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2021

This issue has been marked as stale because it has not seen any activity within the past 60 days. Our team uses this tool to help surface issues for review. If you are the author of the issue there's no need to comment as it will be looked at.

Internal: After 10 days with no activity this issue will be automatically be closed.

@github-actions github-actions bot added the status: stale Stale issues and PRs have had no updates for 60 days. label Nov 4, 2021
@nerrad nerrad removed the status: stale Stale issues and PRs have had no updates for 60 days. label Nov 19, 2021
@github-actions
Copy link
Contributor

This issue has been marked as stale because it has not seen any activity within the past 60 days. Our team uses this tool to help surface issues for review. If you are the author of the issue there's no need to comment as it will be looked at.

Internal: After 10 days with no activity this issue will be automatically be closed.

@github-actions github-actions bot added the status: stale Stale issues and PRs have had no updates for 60 days. label Jan 20, 2022
@Aljullu Aljullu removed the status: stale Stale issues and PRs have had no updates for 60 days. label Jan 23, 2022
@spraveenitpro spraveenitpro mentioned this issue Feb 3, 2022
Closed
@tarunvijwani
Copy link

I'd like to work on this.

@tarunvijwani tarunvijwani mentioned this issue Mar 1, 2022
Closed
1 task
@tarunvijwani
Copy link

Waiting for WordPress/gutenberg#20797 to get resolved.

For more information, please check the PR comment.

@tarunvijwani tarunvijwani added the status: on hold The issue is currently not prioritized or is awaiting something (for example, a fix upsteam). label Mar 3, 2022
@github-actions
Copy link
Contributor

github-actions bot commented May 3, 2022

This issue has been marked as stale because it has not seen any activity within the past 60 days. Our team uses this tool to help surface issues for review. If you are the author of the issue there's no need to comment as it will be looked at.

Internal: After 10 days with no activity this issue will be automatically be closed.

@github-actions github-actions bot added the status: stale Stale issues and PRs have had no updates for 60 days. label May 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@tarunvijwani tarunvijwani

Labels
block: all products Issues related to the all products block. focus: global styles Issues that involve styles/css/layout structure. status: on hold The issue is currently not prioritized or is awaiting something (for example, a fix upsteam). status: stale Stale issues and PRs have had no updates for 60 days. type: good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix sort-select frontend CSS woocommerce/woocommerce-blocks
3 participants
@nerrad @Aljullu @tarunvijwani