- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Jun 2023 12:03:40 +0000
- To: public-css-archive@w3.org
> Ok, two tabs logged out. In one tab you hit the login button and log in. What happens when you hit the login button on the other tab? Perhaps in this case the whole transition would be unexpected. I would expect it to be skipped. I wonder if it could be a "skip on redirect" boolean-ish though it doesn't feel complete. > > But, regardless of this, you shouldn't be betting an API design, that ideally will live for decades, will ideally outlive various frontend and backend patterns, on "well it probably won't happen often". > > Instead, don't cut corners, design the API without easily foreseeable footguns. Sure, just looking to work with valid use cases and make them simple enough. We have to start with the simple common use-cases What I'm struggling with here is the feasibility of making the final URL observable when we enable cross-origin same-site, and if we want to enable something that's incompatible with that. Perhaps if we use the navigation-matchers (#8925) we can make something that affects the style (mainly transition-names) but is not observable to the original document. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8785#issuecomment-1587198949 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 12 June 2023 12:03:42 UTC