- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Jun 2023 12:51:06 +0000
- To: public-css-archive@w3.org
> That's a good use-case, e.g. submitting to`/submit` redirects to `/success` and `/failure`. > I wonder in this case if it's necessary for the original document to differentiate what it captures / under what names. I don't know, but that's only one case. It's also common for `/post-thing` to redirect to the posted thing (or back to the form with error messages), and in that case it is important for the old document to capture particular things. > The concept is not to pretend that redirects don't exist, but to find a solution for this that's forward-compatible with same-site, and explore if the complexity it adds is useful enough. I'd avoid limiting same-origin use-cases due to cross-origin use-cases. -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8785#issuecomment-1587279190 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:51:07 UTC