Re: [csswg-drafts] [css-borders] Standardize groove/ridge/inset/outset border-color computations (#9393)

I just ran into this again while trying to make my site. Here are screenshots of `ridge #111`:

Safari:
![image](https://github.com/user-attachments/assets/aab5367f-36b7-456c-9c9d-ffe67d8ed1b3)

Chrome (they've fixed the hardcoded to gray bug):
![image](https://github.com/user-attachments/assets/801a26d5-32f0-4a5b-b53b-4911d34cb847)

Firefox:
![image](https://github.com/user-attachments/assets/f748470a-482a-47ba-82db-2663cc9ca7cd)


@bert-github @fantasai @LeaVerou @SebastianZ (editors of CSS borders) Can we make an HTML page with a matrix of border colors (including extremes like black and white which have special cases) and see which browser has the most sensible algorithm? That can then be standardized (and bikeshed on)

For `#111`, seems like Safari has the worse result (due to applying double luminance for very dark colors), so WebKit might not be the 100% ideal algorithm. Firefox shows too little contrast (https://bugs.webkit.org/show_bug.cgi?id=261847 would probably filed if this was used widely). Chrome seems to have a sensible result (although the super contrasty colors kind of ruins the 3D effect).







-- 
GitHub Notification of comment by nt1m
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9393#issuecomment-2285337635 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 13 August 2024 04:53:30 UTC