- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Aug 2023 16:41:00 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Dropping :target-within, deprecating :focus-within`, and agreed to the following: * `RESOLVED: Keep :focus-within, replace :target-within with a note that we hope :has(:target) is sufficient for use cases` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: Dropping :target-within, deprecating :focus-within<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/8357<br> <fantasai> TabAtkins: It's possible we can just close this?<br> <fantasai> TabAtkins: Oriol points out that :focus-within has a number of arguments in favor of existence<br> <fantasai> TabAtkins: it operates on flat tree, has better perf, and includes the element itself<br> <fantasai> TabAtkins: Lea agrees<br> <fantasai> TabAtkins: :target-within, given no impl yet might be fine to drop, but I presume it has similar arguments for :focus-within<br> <florian> q+<br> <oriol> q+<br> <emilio> fantasai: In favor of keeping both for the reasons mentioned<br> <TabAtkins> fantasai: I'm in favor of keeping thm both for the reasons given<br> <fantasai> florian: I think we should definitely keep :focus-within, this has very relevant usage<br> <fantasai> florian: before we had :has() there was movement to add various :*-within for other things<br> <fantasai> florian: but now we do have :has(), so I'm less sure about adding more that are not as hot in terms of usage as :focus-within<br> <fantasai> florian: :target-within already in the spec, but no implementation, suggests lesser demand<br> <fantasai> florian: possibly to re-add later, if we observe :has()<br> <fantasai> florian: if too hard to optimize<br> <astearns> ack fantasai<br> <astearns> ack florian<br> <fantasai> florian: but if can do with :has(), seems fine<br> <astearns> ack oriol<br> <fantasai> florian: so I would keep :focus-within and drop :target-within<br> <fantasai> oriol: I agree we should keep :focus-within and drop :target-within<br> <fantasai> oriol: point about flat tree doesn't seem to apply, I couldn't get :target to work with shadow DOM<br> <fantasai> oriol: perf isn't an issue here<br> <astearns> ack fantasai<br> <Zakim> fantasai, you wanted to point out shadow tree aspect<br> <emilio> fantasai: wdym you can't make them work on the shadow dom?<br> <emilio> ... if you have anchors in your shadow tree, you can't make `:target-within` match that<br> <emilio> oriol: I'd need to test again<br> <emilio> q+<br> <fantasai> s/:target-within/:has(:target)/<br> <astearns> ack emilio<br> <fantasai> emilio: having :target match inside a shadow tree doesn't make sense, because URL only works in the outer tree<br> <fantasai> astearns: given lack of implementation, and implementation interest, I'd be OK adding a note saying that we believe :has(:target) is sufficient, but if there's some implication that requires it we might add it back<br> <fantasai> wfm<br> <fantasai> astearns: other opinions?<br> <fantasai> astearns: proposed resolution is to keep :focus-within and replace :target-within with a note that we hope :has(:target) is sufficient for use cases<br> <fantasai> RESOLVED: Keep :focus-within, replace :target-within with a note that we hope :has(:target) is sufficient for use cases<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8357#issuecomment-1680937182 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 August 2023 16:41:03 UTC