Bug 313716
| Summary: | Preserve sticky user activation across same-origin navigations, block carry-over through cross-origin redirects | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | klee |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | ||
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: |
https://bugs.webkit.org/show_bug.cgi?id=312241 https://bugs.webkit.org/show_bug.cgi?id=312719 |
||
klee
Implement sticky user activation carry-over for same-origin navigations, as proposed in whatwg/html#11454.
When a page navigates to another same-origin page, sticky activation(hasBeenActive) should be preserved. However, sticky activation should NOT be carried over when the navigation involves a cross-origin redirect(A -> B -> A2), to prevent confused deputy attacks.
Upstream WPT tests:
- html/user-activation/navigate-to-sameorigin.html
(verifies sticky activation is preserved across same-origin navigations)
- html/user-activation/navigate-to-crossorigin-redirect.html
(verifies sticky activation is NOT preserved through cross-origin redirects)
Related:
- Bug 312241 (WPT test import, resolved)
- Bug 312719 (eventSender popup window support, required for running the tests)
- Spec PR: https://github.com/nicolo-ribaudo/tc39-proposal-structs/pull/11454
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
klee
Pull request: https://github.com/WebKit/WebKit/pull/63952