Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #63030, comment 7


Ignore:
Timestamp:
03/18/2025 10:31:15 PM (15 months ago)
Author:
sabernhardt
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #63030, comment 7

    initial v1  
    1 I have some thoughts to share. The current approach needs to consider compatibility with legacy Firefox versions that still represent about 18% of users. I'd recommend keeping the opacity: 1 property temporarily with a clear deprecation timeline and documenting the planned removal date in code comments. For theme implementation, using
     1I have some thoughts to share. The current approach needs to consider compatibility with legacy Firefox versions that still represent about 18% of users. I'd recommend keeping the `opacity: 1` property temporarily with a clear deprecation timeline and documenting the planned removal date in code comments. For theme implementation, using
    22{{{
    33color-mix(in srgb, currentColor 75%, transparent)
    44}}}
    55
    6 provides better contrast while maintaining compatibility across themes. For the core implementation, we should retain the #646970 color for the admin area while adding progressive enhancement for newer Firefox versions, making sure we meet WCAG AA compliance for color contrast. Theme authors would benefit from guidance on implementing relative color values using color-mix, which automatically supports both light and dark modes.
     6provides better contrast while maintaining compatibility across themes. For the core implementation, we should retain the `#646970` color for the admin area while adding progressive enhancement for newer Firefox versions, making sure we meet WCAG AA compliance for color contrast. Theme authors would benefit from guidance on implementing relative color values using color-mix, which automatically supports both light and dark modes.