[csswg-drafts] [css-view-transitions-2] Namespacing id vs css based view transition names (#11112)

khushalsagar has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-view-transitions-2] Namespacing id vs css based view transition names ==
In https://github.com/w3c/csswg-drafts/issues/10995, we resolved that `auto` will figure out the name for an element based on its id (if available) or fallback to node identity. The question is how the id based name interacts with css based names set up as `view-transition-name: foo`. A possible edge case is where the id on an element collides with the name specified for a different element in CSS.

So the options here are:

1. Id based names are not special, they are treated same as custom idents directly specified in CSS.
2. Id based names are namespaced separately by the UA. The name has a `#` prefix to indicate that it's ID based to be used in CSS and script APIs. For example, `::view-transition-group(#foo)` for an ID based name instead of `::view-transition-group(foo)` for a CSS based name.

I'm more in favour of (1). It's simple to understand, doesn't require knowing the customization code to understand how naming is being done. And I can't think of a use-case where the author would want/need this distinction. They'd likely be sticking to a consistent naming strategy. OTOH, this means that it won't be possible to match an ID based name on one Document with a CSS based name on another Document.

@fantasai @nt1m @emilio @noamr @bramus 

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11112 using your GitHub account


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

Received on Wednesday, 30 October 2024 16:08:49 UTC