惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

AI
AI
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
N
News and Events Feed by Topic
O
OpenAI News
W
WeLiveSecurity
S
Secure Thoughts
www.infosecurity-magazine.com
www.infosecurity-magazine.com
H
Heimdal Security Blog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
Schneier on Security
Schneier on Security
Cloudbric
Cloudbric
T
Threatpost
T
Troy Hunt's Blog
T
Tenable Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
V
Vulnerabilities – Threatpost
Google Online Security Blog
Google Online Security Blog
Recent Commits to openclaw:main
Recent Commits to openclaw:main
The Hacker News
The Hacker News
Know Your Adversary
Know Your Adversary
Forbes - Security
Forbes - Security
Cyberwarzone
Cyberwarzone
C
CXSECURITY Database RSS Feed - CXSecurity.com
P
Privacy & Cybersecurity Law Blog
L
Lohrmann on Cybersecurity
博客园 - 司徒正美
腾讯CDC
博客园 - 三生石上(FineUI控件)
爱范儿
爱范儿
J
Java Code Geeks
Hugging Face - Blog
Hugging Face - Blog
博客园 - 【当耐特】
M
MIT News - Artificial intelligence
T
The Blog of Author Tim Ferriss
MongoDB | Blog
MongoDB | Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
GbyAI
GbyAI
D
Docker
V
Visual Studio Blog
云风的 BLOG
云风的 BLOG
I
InfoQ
WordPress大学
WordPress大学
人人都是产品经理
人人都是产品经理
A
Arctic Wolf
L
LINUX DO - 热门话题
The Cloudflare Blog
雷峰网
雷峰网
Microsoft Azure Blog
Microsoft Azure Blog
小众软件
小众软件

The WHATWG Blog

The WHATWG Blog — The URL Pattern Standard The WHATWG Blog — Retro-specifying fetch/performance The WHATWG Blog — New Living Standards The WHATWG Blog — Newline normalizations in form submission The WHATWG Blog — Update from the Steering Group The WHATWG Blog — Considering accessibility The WHATWG Blog — Focusing on focus The WHATWG Blog — The state of fieldset interoperability The WHATWG Blog — First set of Review Drafts published
The WHATWG Blog — Staged proposals at the WHATWG
Domenic Deni · 2025-04-28 · via The WHATWG Blog

Staged proposals at the WHATWG

by Domenic Denicola in WHATWG

The WHATWG's living standards incorporate new features on an ongoing basis. The default process is to propose an idea on the relevant standard's issue tracker, hash out the details and gather implementer interest, and then work together with the editors to land a pull request.

However, we've found that for larger features, or for community members less experienced with standards contributions, sometimes this lightweight process does not give enough guidance. It can be tricky to attract attention to one's proposal, or to get the clear signals from implementers that are necessary to land changes.

Inspired by other working groups, most notably the TC39 group that defines the JavaScript language, the WHATWG community has established a new, optional Stages process for additions to WHATWG standards. Features can proceed from stage 0, where they just consist of a problem description, through to stage 4, when the feature has fully landed in the relevant living standard. Each stage requires increasing levels of community consensus, including from implementers and from the standard's editors. This gives the proposer, as well as the community, a better idea of a feature's progress towards being considered an accepted part of the web platform.

We've now had the Stages process for over a year. As of today, one proposal, the node.moveBefore() atomic move operation, has advanced to stage 4; one, for the customizable <select> element, has advanced to stage 3; and six others are in stages 2 and 1 combined. These numbers might not seem that high, but remember that the stages process is optional: we've landed many other proposals via the usual pull request process. We're happy with the balance we've achieved so far, with certain complex proposals using the stages process while other proceed directly to a pull request.

For more information on the Stages process, including its motivation, mechanics, and each stage's entrance criteria, see its dedicated page. Readers may also enjoy reading our discussion about how TC39 stages and WHATWG stages differ, in light of the groups' different working modes.

Finally, we'd like to thank Chris Harrelson for proposing the idea of a stages process in the first place, Chris Wilson for writing up the process, and TC39 for providing a useful model to follow.