- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Dec 2024 21:57:08 +0000
- To: public-css-archive@w3.org
> @fantasai can you comment on auto in your 18.2 release? I believe what happened is that there was [agreement on adding it](https://github.com/w3c/csswg-drafts/issues/8320) [as re-iterated in the OP above](https://github.com/w3c/csswg-drafts/issues/10995#issue-2563372075), it was [added to the spec](https://github.com/w3c/csswg-drafts/pull/10922), the WebKit team promptly implemented it in good faith [as published in the spec](https://www.w3.org/TR/2024/WD-css-view-transitions-2-20241113/#additions-to-vt-name) and tested in WPT, and the objection subsequently raised here was too late to make any changes to the release. > However, I also want to ensure that we add match-element/match-element() as a keyword for non-id matching behavior. I believe we have consensus on that across all parties (correct me if I'm wrong). Not an objection, but, what is the use case for `match-element` if we already have `auto`? Like, what's a _realistic_ example of a page which would need `match-element` with the ID-matching behavior specifically disabled? -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10995#issuecomment-2549723766 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 December 2024 21:57:08 UTC