Add logic to update radio button group checkedness when an input radio becomes connected

[EdgarChen]

Closes #10897.

• At least two implementers are interested (and none opposed):
  • Chromium and WebKit already behave like this.
• Tests are written and can be reviewed and commented upon at:
  • [Gecko Bug 1938489] Don’t update other radio inputs in the same radio group when a radio input is appended to a disconnected subtree web-platform-tests/wpt#50048
• Implementation bugs are filed:
  • Chromium: None
  • Gecko: https://bugzilla.mozilla.org/show_bug.cgi?id=1938489
  • WebKit: None
  • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): None
  • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): None
• Corresponding HTML AAM & ARIA in HTML issues & PRs: N/A
• MDN issue is filed: N/A
• The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)

---

/input.html ( diff )

[EdgarChen]

cc @domfarolino @annevk

[domfarolino]

LGTM. One question: the issue mentions:

However, all browsers also update the checkedness state of elements in the same radio button group when the element becomes connected

But you also have an implementation bug filed for Firefox. Do any implementations need to do any work for this, or is this PR just bringing the spec inline with what all browsers do?

[EdgarChen]

Our (Firefox) implementation bug is filed to align our behavior with other browsers for the case where a radio input is inserted into a disconnected radio group. Previously, we would also run the steps to update the checkedness state, but other browsers don’t. And this PR bring the spec inline with what all browsers do currently.