> I believe in WPT we can't have an a.html top-frame navigate to b.html and 
> check things there.  I was not able to find an example in 
> wpt/navigation-api/.  Did I miss anything?

I think it’s correct that we can’t test it with top-level navigations, but can 
we test it for iframe navigations? The way I understand 
https://github.com/whatwg/html/pull/11454 iframe navs should also get the new 
behavior.

From: Mustaq Ahmed <mus...@chromium.org>
Sent: Tuesday, September 2, 2025 11:04 AM
To: Daniel Clark <dan...@microsoft.com>
Cc: Chromestatus <ad...@cr-status.appspotmail.com>; blink-dev@chromium.org; 
vmp...@chromium.org
Subject: Re: [EXTERNAL] [blink-dev] Intent to Ship: Sticky user activation 
across same-origin navigations



On Thu, Aug 28, 2025 at 9:45 PM Daniel Clark 
<dan...@microsoft.com<mailto:dan...@microsoft.com>> wrote:
> Gecko: Positive 
> (https://github.com/WICG/view-transitions/issues/239#issuecomment-2851155373)
> WebKit: Positive 
> (https://github.com/whatwg/html/issues/11328#:~:text=anne%3A%20sounds%20good.%20i%20dont%20think%20we%20will%20regret%20this%2C%20but%20we%20will%20have%20to%20test%20it%20carefully)

It’d be good to have official standards 
positions<https://www.chromium.org/blink/launching-features/wide-review/#standards-positions>
 filed or at least to get Gecko and WebKit signoff on the spec PR. I agree from 
the notes that the sentiment looks positive but statements like “I don’t think 
we will regret this” are not as firm as I’d like :).

 The spec PR is currently under review from Gecko.  I would give it some time 
to settle.


>  Is this feature fully tested by 
> web-platform-tests<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
> No

Could you add WPTs for this?

I believe in WPT we can't have an a.html top-frame navigate to b.html and check 
things there.  I was not able to find an example in wpt/navigation-api/.  Did I 
miss anything?


> Finch feature name
> None
This would be shipped gated by a flag, right?

Thanks for the catch.  I corrected the chromestatus entry to 
"StickyUserActivationAcrossSameOriginNavigation".

-- Dan


From: blink-dev@chromium.org<mailto:blink-dev@chromium.org> 
<blink-dev@chromium.org<mailto:blink-dev@chromium.org>> on behalf of 
Chromestatus 
<ad...@cr-status.appspotmail.com<mailto:ad...@cr-status.appspotmail.com>>
Date: Thursday, August 28, 2025 at 1:17 PM
To: blink-dev@chromium.org<mailto:blink-dev@chromium.org> 
<blink-dev@chromium.org<mailto:blink-dev@chromium.org>>
Cc: vmp...@chromium.org<mailto:vmp...@chromium.org> 
<vmp...@chromium.org<mailto:vmp...@chromium.org>>, 
mus...@chromium.org<mailto:mus...@chromium.org> 
<mus...@chromium.org<mailto:mus...@chromium.org>>
Subject: [EXTERNAL] [blink-dev] Intent to Ship: Sticky user activation across 
same-origin navigations
Contact emails
mus...@chromium.org<mailto:mus...@chromium.org>
Explainer
None
Specification
https://github.com/whatwg/html/pull/11454
Summary

This feature preserves the sticky user activation state after a page navigates 
to another same-origin page. The lack of user activation in the post-navigation 
page prevents some use cases like showing virtual keyboards on auto-focus, and 
this has been a blocker for the developers who want to build MPAs over SPAs.

Blink component
Blink>Input<https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EInput%22>
TAG review
None
TAG review status
Pending
Risks

Interoperability and Compatibility

None


Gecko: Positive 
(https://github.com/WICG/view-transitions/issues/239#issuecomment-2851155373)

WebKit: Positive 
(https://github.com/whatwg/html/issues/11328#:~:text=anne%3A%20sounds%20good.%20i%20dont%20think%20we%20will%20regret%20this%2C%20but%20we%20will%20have%20to%20test%20it%20carefully)

Web developers: Positive (https://github.com/WICG/view-transitions/issues/239)

Other signals:
WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it 
has potentially high risk for Android WebView-based applications?

None

Debuggability

None

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, 
ChromeOS, Android, and Android WebView)?
Yes
Is this feature fully tested by 
web-platform-tests<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
No
Flag name on about://flags
None
Finch feature name
None
Non-finch justification
None
Rollout plan
Will ship enabled for all users
Requires code in //chrome?
False
Tracking bug
https://issues.chromium.org/433729626
Sample links

https://vmpstr.github.io/htmldemos/activation/a.html
Estimated milestones
Shipping on desktop
142
Shipping on Android
142
Shipping on WebView
142

Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop 
issues. Please list open issues (e.g. links to known github issues in the 
project for the feature specification) whose resolution may introduce web 
compat/interop risk (e.g., changing to naming or structure of the API in a 
non-backward-compatible way).
None
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5078337520926720?gate=5110603664064512
This intent message was generated by Chrome Platform 
Status<https://chromestatus.com/>.
--
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
blink-dev+unsubscr...@chromium.org<mailto:blink-dev+unsubscr...@chromium.org>.
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68b0b943.050a0220.270bc4.0090.GAE%40google.com<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68b0b943.050a0220.270bc4.0090.GAE%40google.com?utm_medium=email&utm_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/DS0PR00MB2342DC14AF7D4DA241E3F718C501A%40DS0PR00MB2342.namprd00.prod.outlook.com.

Reply via email to