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

The CSS Working Group just discussed `[css-selectors-4] browser focus styles and focus-visible, example 38`, and agreed to the following:

* `RESOLVED: remove the example`

<details><summary>The full IRC log of that discussion</summary>
&lt;myles> Topic: [css-selectors-4] browser focus styles and focus-visible, example 38<br>
&lt;myles> GitHub: https://github.com/w3c/csswg-drafts/issues/4278<br>
&lt;myles> rego: florian reported it, but I added it to the agenda<br>
&lt;myles> rego: florian was asking about focus-visible in the spec. Was asking about using focus-visible to remove the old line from the element<br>
&lt;myles> rego: The thing is that, this was confusing to some people, and kind of a hack to disable the whole line instead of the focus when you have focus visible, to see the whole line but not always<br>
&lt;myles> rego: this is kind of confusing. you expect when it matches focus-visible, it matches only when the outline is painted.<br>
&lt;myles> rego: and if it's not painted it's not<br>
&lt;myles> rego: chromium was not using that in its default visible. So you would get an outline but the element wasn't matching focus-visible<br>
&lt;florian> q+<br>
&lt;myles> rego: Chromium's impl is updated. The default stylesheet uses focus-visible. So this example can be removed from the spec. Because it was only due to some browsers' implementations.<br>
&lt;myles> florian: We should double remove it.<br>
&lt;myles> florian: This is no longer how browsers work. It shouldn't stay there. Also, even when we were before that change, specs are a bad place to put descriptions of hacks you need to use to force browsers to not follow the spec behave correctly. And if we do that, it needs to be described deliberately<br>
&lt;myles> florian: now that it's no longer relevant, remove it, and if we need to highlight workarounds in the spec, be clear they are workarounds.<br>
&lt;Rossen_> q?<br>
&lt;Rossen_> ack florian<br>
&lt;myles> rego: So the proposal is to remove the example from the sepc<br>
&lt;myles> bkardell_: We should remove it. My recollection is that we added that to help people understand what it was doing, because you could explain that focused matched all the time, and people said it this way, but people wanted to remove it when that wasn't the case. but that made it into the spec in a way that it should not have. we should take it out.<br>
&lt;myles> Rossen_: proposed resolution: remove the example<br>
&lt;fantasai> If we agree on something, we resolve on it, so it's clear there was an agreement.<br>
&lt;myles> RESOLVED: remove the example<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4278#issuecomment-776112220 using your GitHub account


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

Received on Tuesday, 9 February 2021 17:36:52 UTC