Re: [csswg-drafts] [css-contain-2] Should CSS highlights make content relevant to the user? (#9277)

The CSS Working Group just discussed `[css-contain-2] Should CSS highlights make content relevant to the user?`, and agreed to the following:

* `RESOLVED: Change the line about selection to link to the selection API instead of highlight pseudo element`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> vmpstr: In contain2 spec we have text what 'relevent to the user' means. One point is if element or content is selected it's relevent and then links to a highlight pseudo<br>
&lt;TabAtkins> +1 to this<br>
&lt;dael> vmpstr: I think that's misleading. Instead I think it should link to the selection API which goes into details on how a selection acts. I think it's more appropriate<br>
&lt;schenney> +1<br>
&lt;dael> Rossen_: Sounds reasonable<br>
&lt;dael> Rossen_: What do other folks think?<br>
&lt;schenney> q+<br>
&lt;Rossen_> ack schenney<br>
&lt;dael> schenney: Clarification: if there's target text it will be scrolled to and will open up? That's the only other pseudo taht came to mind as potentially useful.<br>
&lt;dael> schenney: If we have target-text from URl target is that considered user relevant already?<br>
&lt;dael> vmpstr: Yeah, that should be. For content-visibility:auto where relevance matters the skipped contents are still available to features like tab order navigation and find in page.<br>
&lt;dael> schenney: Okay, so I think we're good with the proposal<br>
&lt;dael> Rossen_: Other opinions?<br>
&lt;dael> vmpstr: Prop: Change the line about selection to link to the selection API instead of highlight pseudo element<br>
&lt;dael> Rossen_: Objections?<br>
&lt;dael> RESOLVED: Change the line about selection to link to the selection API instead of highlight pseudo element<br>
</details>


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


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

Received on Thursday, 7 September 2023 00:02:10 UTC