Define form-owner updates through DOM hooks Replace scattered form-owner mutation requirements with explicit HTML insertion, removing, moving, and attribute change steps. Define affected trees and tree-order processing, limiting ID-triggered resets to connected trees and controls whose `form` values match an affected ID. Fix missing ancestor-form fallback when form-attribute controls disconnect and missing reassociation when they move between trees. Compute the replacement form owner before changing the association, doing nothing when it is unchanged; this prevents reassociation between forms from temporarily joining the ownerless radio group and unchecking unrelated radios. (All browsers currently uncheck unrelated radios in disconnection cases, but we are intentionally changing that.) Custom-element reaction ordering, disabledness updates, and broader same-tree/parser-established association behavior during moves remain out of scope; see https://github.com/whatwg/html/issues/13185. Helps with https://github.com/whatwg/html/issues/10331. Co-authored-by: codex <codex@openai.com> Co-authored-by: Anne van Kesteren <annevk@annevk.nl>
Current
·
C2
·2026-11
Define form-owner updates through DOM hooks
Find Your Interest
- fix: avoid waiting for stopped Gateways during updates
- Phoenix Suns vs Sacramento Kings. Live updates, NBA analysis
- The Forms Evolution, Web AI, and Architectural Vision!
- The Forms Evolution, Web AI, and Architectural Vision!
- Ubuntu包管理
- On the web, data doesn’t define us. It creates us.
- How to Maximize Your Video Content
- Cryptocurrency-Based Life Form
- Full practice for Saquon Barkley
- Washington vs Utah Tech live updates: Score, highlights, predictions, analysis
Current
·
C2
·2026-11






