- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jun 2024 11:02:46 +0000
- To: public-css-archive@w3.org
> The pattern above already exists in SPAs today, and in order to easily transform SPAs to MPAs we'll need some simple mechanism to eliminate the need for keeping that state in user-land. Are SPAs doing it by keeping this in user-land? The idea seems reasonable to me and should be trivial to add for cross-document navigations. Its the CSS equivalent of [NavigationActivation](https://html.spec.whatwg.org/multipage/nav-history-apis.html#navigation-activation-interface) so we should probably go for a syntax that allows adding other stuff from NavigationActivation to CSS. But I'm not sure how to reason about it for the SPA case. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10434#issuecomment-2162724261 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 June 2024 11:02:47 UTC