← back to v142 · sticky-user-activation-across-same-origin-renderer-initiated-navigations
conformance · v142
v142 · sticky-user-activation-across-same-origin-renderer-initiated-navigations — conformance probe
6 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
user-activation-on-navigator |
navigator.userActivation is exposed; this is the introspection surface for both transient and sticky activation. | script | … | |
user-activation-has-sticky |
UserActivation exposes a hasBeenActive boolean — the sticky bit that is now preserved across same-origin renderer-initiated navigations. | script | … | |
user-activation-has-transient |
UserActivation also exposes isActive (transient); the new behaviour only carries the sticky bit, not the transient bit. | script | … | |
user-activation-types-are-boolean |
Both hasBeenActive and isActive are booleans. | script | … | |
navigation-api-exists |
The Navigation API is the modern surface for renderer-initiated navigations that this change applies to. | script | … | |
fresh-load-without-interaction-not-sticky |
On a fresh load with no user interaction, hasBeenActive is false. (After this change, that bit can be true on a navigated-to same-origin page that inherits activation.) | script | … |