W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2019

[csswg-drafts] [css-selectors-4] browser focus styles and focus-visible, example 38 (#4278)

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Thu, 05 Sep 2019 04:17:26 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-489518727-1567657045-sysbot+gh@w3.org>
frivoal has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-selectors-4] browser focus styles and focus-visible, example 38 ==
My understanding of :focus-visible was that it gave authors access to the existing logic by which browsers style focused elements, so that authors could change that, without adding focus indicators onto things where the browser wouldn't, which is what would happen if they used :focus instead.

However, the spec, and in particular example 38, suggest that authors could write something like:
:focus:not(:focus-visible) {
  outline: 0;
in order to suppress browser-supplied focus indicators on elements that match :focus but not :focus-visible.

That's very confusing to me, as by my understanding, there should be no such element. The sentence immediately before the example also seems to agree with me.

Maybe that selector is meant as a poor man's `@support` for selectors, but it's given what the rest of the example does, it's not needed or useful.

If I'm right, this example is [causing confusion](https://github.com/mozdevs/cssremedy/issues/26#issuecomment-466283191) and inducing authors to think that they need to use `:focus:not(:focus-visible)` to select and suppress undesirable browser styles, which is just not true. In that case, this should be removed from the example.

If I'm wrong, I'd like to understand why, because then the feature no longer makes sense to me.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4278 using your GitHub account
Received on Thursday, 5 September 2019 04:17:28 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:53 UTC