Re: [blink-dev] Intent to Ship: view-transition-name: auto

I remain unconvinced that the benefits of this feature (the ability to "magically" get transitions across documents) outweigh its ecosystem costs (footgun around the use of IDs, partial application of transitions in the cross-document case). At the very least, it seems like the name of the feat

Re: [blink-dev] Intent to Ship: view-transition-name: auto

LGTM1, even if the name changes from `auto` to something else. Adding or removing an ID to a dom element (or a class even) may always carry the risk of breaking behavior or styling in a page. Perhaps this is more likely in certain types of apps, perhaps not. I don't think we're treading new gr

[blink-dev] Intent to Ship: view-transition-name: auto

Contact emailsvmp...@chromium.org, nrosent...@chromium.org Explainer https://github.com/WICG/view-transitions/blob/main/auto-name-explainer.md Specificationhttps://drafts.csswg.org/css-view-transitions-2/#auto-vt-name Blink componentBlink>ViewTransitions