Opened 10 months ago
Closed 6 months ago
#63196 closed enhancement (fixed)
Typo correction
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 6.9 | Priority: | normal |
| Severity: | minor | Version: | 4.9 |
| Component: | Administration | Keywords: | has-patch commit |
| Focuses: | css, docs | Cc: |
Description
Typo correction in CSS comment.
Change History (9)
This ticket was mentioned in PR #8617 on WordPress/wordpress-develop by @mujuonly.
10 months ago
#1
- Keywords has-patch added
#2
@
10 months ago
- Component changed from General to Administration
- Focuses docs added
- Milestone changed from Awaiting Review to 6.9
- Version set to 4.9
[41329] added the comment 'Needs higher specificiity.'
Because this ticket is labeled an enhancement, explaining which selector the higher specificity overrides could be more helpful. Or else it might say how many classes it needs.
39662.diff included the comment when it changed .wp-color-result to .wp-picker-container .wp-color-result, and 39662.2.diff added a third class (.wp-picker-container .wp-color-result.button).
#3
@
10 months ago
It seems to need at least two classes to override .wp-core-ui .button in the Customizer.
#4
@
10 months ago
- Keywords changes-requested added
- Owner set to audrasjb
- Status changed from new to accepted
Yes, let's take advantage of this ticket to clarify this docblock.
#5
@
6 months ago
Comment Suggestion:
/* * Requires at least two class-level selectors (e.g., * '.wp-picker-container .wp-color-result') to override the * '.wp-core-ui .button' style in the Customizer. * Add a third class (e.g., '.button') for increased specificity. */
or a bit short:
/* Use .wp-picker-container .wp-color-result to override .wp-core-ui .button */
Typo correction
Trac ticket: https://core.trac.wordpress.org/ticket/63196