- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Apr 2020 16:26:35 +0000
- To: public-css-archive@w3.org
I'm the one who filed the original Chromium bug report. It was an issue for me because I _used_ to be able to reliably improve the contrast and position of a focus outline in most browsers by setting the outline properties other than `outline-style`. I specifically avoided setting `outline-style` because it overrides the browser's focus-visibility heuristics. (This would be less of an issue if [`:focus-visible` had better browser support](https://developer.mozilla.org/en-US/docs/Web/CSS/:focus-visible#Browser_compatibility).) Over the past few years, more browsers have switched from using standard CSS outlines to using these glowy default focus outlines which frequently fail contrast requirements, and which cannot reliably be modified by setting the individual sub-properties. Content that previously had useful focus outlines now is broken. But… for whatever reasons, all the browsers are standardizing around these faded, WCAG non-compliant focus glow effects. So at the very least CSS should warn authors about it. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4925#issuecomment-610487670 using your GitHub account
Received on Tuesday, 7 April 2020 16:26:38 UTC