- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Jun 2023 12:46:52 +0000
- To: public-css-archive@w3.org
> Redirects are also common on form submissions. > I don't think this feature should pretend they aren't part of the platform, or hope that part of the platform isn't used. 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. Perhaps the only difference this would make is some redundant captures? 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. Having something that affects the style/transition names but is not observable by the old document might be a feasible direction (e.g. the media query proposed in #8925 applies the final URL to the style but there's no JS event). -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8785#issuecomment-1587273447 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:46:54 UTC