mdn/content

Update sticky activation docs for new spec changes to carry across pages

Open

#41241 opened on Sep 18, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Markdown (8,900 stars) (22,427 forks)batch import
Content:GlossaryContent:SecurityContent:WebAPIhelp wanted

Description

Proposal

In https://github.com/whatwg/html/pull/11454, we are updating sticky activation to carry across same-origin navigations and traversals. The docs at https://developer.mozilla.org/en-US/docs/Glossary/Sticky_activation should be updated to reflect this.

Browser support

This is being prepared to ship in Chromium, almost certainly version 142.

WebKit and Gecko are positive but I don't know about concrete engineering milestones.

Tasks

Dependencies

No response

Additional information

https://github.com/whatwg/html/pull/11454 contains (or will soon contain) links to browser implementation bugs and web platform tests.

Are you willing to support this work?

Sorry, I am retiring soon and won't have time to provide reviews! @mustaqahmed might be able to help though

Contributor guide

Tech stack
htmlcssjavascript
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of sticky activationFamiliarity with MDN documentation processBasic knowledge of web platform specs
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Review the WHATWG HTML spec PR (whatwg/html/pull/11454) to understand the changes to sticky activation. Then update the MDN glossary page (Glossary/Sticky activation) and possibly the user activation pages (Web/Security/User activation and Web/API/UserActivation). Check the Chromium shipping announcement for browser support details, and look at the linked web platform tests for concrete examples.