Skip to content

Sticky user activation across same-origin navigations #1295

Closed

Description

@mustaqahmed

Specification title

Sticky user activation across same-origin navigations

Specification or proposal URL (if available)

whatwg/html#11454

Explainer URL (if available)

No response

Proposal author(s)

@mustaqahmed

MDN URL

No response

Caniuse.com URL

No response

Bugzilla URL

No response

Mozillians who can provide input

@smaug----

WebKit standards-position

WebKit/standards-positions#547

Other information

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.

Activity

  1. moved this from Unscreened to Position is proposed in standards-positions reviewon Sep 10, 2025
  2. smaug---- commented on Sep 10, 2025

    @smaug----
    Collaborator

    We're positive on this, but need to review the spec PR still. The earlier variant wasn't dealing with BFCache.
    (Positive standards-position does not mean the spec is ready to ship)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions