Opened 4 years ago
Closed 4 years ago
#50536 closed defect (bug) (fixed)
Fix link colors for admin schemes that personalize it using the $link SASS variable
Reported by: | youknowriad | Owned by: | youknowriad |
---|---|---|---|
Milestone: | 5.5 | Priority: | normal |
Severity: | normal | Version: | 5.5 |
Component: | Administration | Keywords: | needs-patch |
Focuses: | css | Cc: |
Description
Custom link colors used on admin schemes are broken in some instances. They are using the default link color.
- For button links
- And a specific case in the customizer
Attachments (5)
Change History (14)
This ticket was mentioned in PR #378 on WordPress/wordpress-develop by youknowriad.
4 years ago
#1
- Keywords has-patch added
https://core.trac.wordpress.org/ticket/50536
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See [GitHub Pull Requests for Code Review](https://make.wordpress.org/core/handbook/contribute/git/github-pull-requests-for-code-review/) in the Core Handbook for more details.
#4
@
4 years ago
- Keywords needs-patch added; has-patch removed
- Resolution fixed deleted
- Status changed from closed to reopened
- Version changed from 5.4 to trunk
[48332] introduced a regression: some "destructive action" buttons aren't red any longer, in all the color schemes.
This happens because now button-link
from the color schemes overrides button-link-delete
.
Red destructive action controls are a well established convention in core, as any potentially action that deletes content should be visually well distinguished.
See attached screenshot for the destructive action in the Widgets. Happens also in the customizer.
Worth also reminding that when changing variables in the _admin.scss
file, the change will likely impact plugins that extend the color schemes. At the very least, this change should have a dev-note.
Reopening as the red color for destructive action should be restored.
#7
@
4 years ago
@youknowriad I'm afraid I'm a bit busy, Beta 1 day :)
Given this is a new feature introduced in this release cycle, I think it can be addressed also during Beta.
The close link was broken.