- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Mar 2025 16:09:27 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-view-transitions-2] view-transition-name: auto when matching id should namespace`, and agreed to the following: * `RESOLVED: v-t-name:auto never matches an explicit v-t-name:<ident>` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> vmpstr: we added v-t-name:auto<br> <TabAtkins> vmpstr: matches the VT name based on the element's ID attribute, and acts as match-element otherwise<br> <TabAtkins> vmpstr: this name isn't exposed anywhere, it's "auto" in serializations<br> <TabAtkins> vmpstr: but wanted to clarify that the ID ident shouldn't match another VT that specifies a manual ident that happens tob e the same<br> <TabAtkins> vmpstr: Like `v-t-name: foo` on one element and `v-t-name:auto` on an element with id="foo" shouldn't match<br> <TabAtkins> astearns: looks like there's agreement in the thread<br> <TabAtkins> sounds fine to me<br> <TabAtkins> astearns: anyone in the room actually want the behavior we're prohibiting?<br> <TabAtkins> no opinion either way, really, happy to defer to editors<br> <bkardell_> makes sense<br> <noamr> +1<br> <TabAtkins> fantasai: I thought that's what we'd adopted originally, that the ID would only be used to link elements together, not something exposeable to other CSS. So this makes sense to me.<br> <TabAtkins> vmpstr: proposed: v-t-name:auto will never match an explicit v-t-name:<ident><br> <TabAtkins> astearns: any objections?<br> <TabAtkins> RESOLVED: v-t-name:auto never matches an explicit v-t-name:<ident><br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11614#issuecomment-2718399971 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 March 2025 16:09:28 UTC