- From: Tim Nguyen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Nov 2024 23:36:38 +0000
- To: public-css-archive@w3.org
@jakearchibald I don't think single-page use cases and multi-page use cases are the same. Your assumption is that they are the same, but I don't see that be the case in the future. Here are some single-page use cases of view transitions: https://codepen.io/smashingmag/full/BabaBKz https://codepen.io/argyleink/pen/dyLNgpX https://codepen.io/argyleink/pen/ZEmLrze Here are multi-page use cases: https://astro-records.pages.dev https://spotify-astro-transitions.vercel.app > Yes but the current auto proposal behaves unpredictability, therefore becomes hard to author. It's surely not optimized for someone converting between SPA & MPA, but I think it's more than reasonable for the use cases above. Realistically, all the use cases you envision to be similar between SPA & MPA will become MPAs in the future, so it makes sense to consider the most realistic use-cases of each type, rather than trying to optimize for the conversion between an outdated practice to a newer practice. Given the use cases are different, I think it's OK to have the behavior for SPAs and MPAs be different, especially for a value like `auto`. -- GitHub Notification of comment by nt1m Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10995#issuecomment-2458413542 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 5 November 2024 23:36:39 UTC