Five dated news digests and five engineering Q&A entries. Each item cites primary documentation or release artifacts (not generic placeholders).
The HTML Standard’s January 2025 review draft mirrors the living standard at a fixed point for legal review—not a separate browser implementation target.
Engineers should continue to implement the current living standard URL for day-to-day work.
Later 2025 drafts follow identical rules: they exist for patent policy obligations and may omit the freshest editor fixes present in the living tree.
Use them when counsel requests a dated snapshot, not when authoring tutorials.
MDN’s HTML attribute references link back to WHATWG definitions for attributes like loading, fetchpriority, and form control behaviors.
When in doubt, open the algorithm sections instead of relying on secondary summaries.
HTML-heavy applications (drag-and-drop, ranges, mutation observers) often require cross-reading the DOM Standard review drafts when filing browser bugs.
Attach both HTML and DOM snapshot links to WHATWG issues for clarity.
While WHATWG defines HTML behavior, mixed content upgrade rules and secure contexts intersect with W3C/WHATWG security documentation that MDN summarizes.
Security engineers should read primary fetch/mixed-content specs when tuning CSP.
No—WHATWG explicitly directs implementers to the living standard; review drafts freeze text for patent review and can miss subsequent corrections.
Use review drafts only for legal or compliance comparisons.
Quote the WHATWG element definitions for native roles, then map them to WAI-ARIA Authoring Practices patterns when composite widgets are unavoidable.
Keep permalinks to specific multipage sections for audit trail clarity.
The living standard evolves; browsers ship at different cadences. Consult browser release notes plus the HTML issue tracker when discrepancies appear.
Automate visual regression tests for form controls especially.
The HTML multipage spec hosts the template section describing inert subtree behavior and parsing rules that shadow DOM polyfills depended on.
MDN summarizes but should not replace spec links in security reviews.
Forms rely on DOM events and ranges; when a regression spans layers, file issues with repro steps against both specs’ living URLs.
Include reduced HTML and JS that only touches public APIs.