We have two places in core where we make users choose options:
Again do we want to have separate colors for this or not? It's presumably going to be hard to have a color that gives A11y compliance in both light and dark modes.
Labels |
Added:
No Code Attached Yet
|
@HLeithner @wilsonge I'm not convinced that there such a need for another colour. Here's my take with Muta
Labels |
Added:
Release Blocker
|
I’m marking this one as a release blocker as whether we merge the color changes or not these template params need dealing with
these template params need dealing with
There's still a need to deal with the -rgb
vars for these colours. In muta I'm doing it directly in the js of the field but for atum (due to b/c) there should be some update fn in the PHP to introduce these values in the db table styles. For ref: https://github.com/dgrammatiko/muta/blob/d6eb3f2f5d12700ae4d461f6fbe5d3cacf266684/media_source/templates/administrator/muta/js/dgcolor-field.mjs#L121-L130
Labels |
Added:
Dark Mode
|
Labels |
Added:
bug
|
Labels |
Removed:
Release Blocker
|
as far as I can tell btn-secondary no longer uses the special colour
Looks like this can be closed
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2024-07-24 16:00:43 |
Closed_By | ⇒ | wilsonge |
Different color make sense i think