#61630 closed defect (bug) (fixed)
Elements: Maintain backwards compatibility by avoiding specificity bump for top-level element-only selectors
Reported by: | aaronrobertshaw | Owned by: | noisysocks |
---|---|---|---|
Milestone: | Priority: | high | |
Severity: | normal | Version: | 6.6 |
Component: | Editor | Keywords: | gutenberg-merge has-patch has-unit-tests |
Focuses: | Cc: |
Description
When CSS specificity was capped at 0-1-0
for global styles via https://core.trac.wordpress.org/ticket/61165 it resulted in top-level element styles in some case having their specificity raised from 0-0-1
.
This can be avoided and greater backwards compatibility maintained.
More info on the issue this causes can be found in:
This ticket tracks the syncing of PHP changes for the fix contained in:
Change History (13)
This ticket was mentioned in PR #7012 on WordPress/wordpress-develop by @aaronrobertshaw.
4 months ago
#1
- Keywords has-patch has-unit-tests added
This ticket was mentioned in Slack in #core by hellofromtonya. View the logs.
4 months ago
#4
@
4 months ago
- Priority changed from normal to high
Elevating the priority to high
for better tracking, as this issue is one of the drivers for a faster 6.6.1.
Testing has been happening on #61660 with good confirmation it resolves that issue.
@noisysocks commented on PR #7012:
4 months ago
#5
Applied the diff of this PR to the 6.6 branch and followed the testing instructions. Looks ok 👍
#6
@
4 months ago
- Owner set to noisysocks
- Resolution set to fixed
- Status changed from new to closed
In 58749:
#7
@
4 months ago
- Keywords dev-feedback added
- Resolution fixed deleted
- Status changed from closed to reopened
Reopening for backporting to the 6.6 branch.
#8
@
4 months ago
- Milestone 6.6.1 deleted
- Resolution set to duplicate
- Status changed from reopened to closed
Confusing that there's two tickets. Let's close this as a dupe of #61660 which has more comments.
@noisysocks commented on PR #7012:
4 months ago
#9
Committed in r58749.
Related #61660.