- From: Tim Nguyen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Nov 2024 17:16:11 +0000
- To: public-css-archive@w3.org
> Sounds like this is a bit of an attempt to "favor" cross-document HTML-first apps over JS-based single-page apps. You know I appreciate that sentiment and I would very much like to find interesting solutions to this problem (if we see that attr doesn't cut it), but I think that match-by-ID is a bit too particular to be it. There is a good reason to do so, JS based apps can attach whatever view-transition-name they want programmatically via script. If the person is using a JS framework, there's a great chance that will be abstracted away anyway. > I don't see why folks are desperate to attach a behaviour to auto today. I think we'll discover much more interesting opportunities in future. I do think it is useful having an `auto` value that tries to do the right thing on your behalf, especially to reduce the need for complex JS or CSS syntax. Let's try to discuss this more on the call to see how this should look like. -- GitHub Notification of comment by nt1m Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10995#issuecomment-2460350975 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 November 2024 17:16:12 UTC