Integrate OpaqueRange hooks into text controls (input/textarea)

[stephanieyzhang]

OpaqueRange is a specialized, live AbstractRange subtype whose boundary points reference internal nodes within host-defined elements (e.g., <input>/<textarea> today, with a path to custom elements in the future). It enables range-based operations over encapsulated content while avoiding exposure of internal DOM nodes.

• Explainer: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/OpaqueRange/explainer.md

• WhatWG discussion: FormControlRange Interface #11478

• Corresponding DOM Spec PR: Add OpaqueRange interface dom#1404

• Corresponding CSSOM PR: [cssom-view-1] Define OpaqueRange geometry APIs (getClientRects/getBoundingClientRect) w3c/csswg-drafts#12904

• At least two implementers are interested (and none opposed):

  • Microsoft Edge
  • WebKit: OpaqueRange: AbstractRange subtype for encapsulated content (<input>, <textarea>) WebKit/standards-positions#541
  • Mozilla: OpaqueRange: AbstractRange subtype for encapsulated content (<input>, <textarea>) mozilla/standards-positions#1289

• Tests are written and can be reviewed and commented upon at:

  • https://wpt.fyi/results/dom/ranges/tentative?label=master&label=experimental&aligned
  • PR to make tests non-tentative: Coming soon

• Implementation bugs are filed:

  • Chromium: https://issues.chromium.org/issues/421421332
  • Gecko: https://bugzilla.mozilla.org/show_bug.cgi?id=1990256
  • WebKit: https://bugs.webkit.org/show_bug.cgi?id=299375

• Corresponding HTML AAM & ARIA in HTML issues & PRs:

• MDN issue is filed: …

• The top of this comment includes a clear commit message to use.

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

---

/form-control-infrastructure.html ( diff )
/form-elements.html ( diff )
/infrastructure.html ( diff )
/input.html ( diff )

[annevk]

Where is "supports opaque ranges" defined?

[stephanieyzhang]

Where is "supports opaque ranges" defined?

Whoops, forgot to define that 🤦. Added it to the "APIs for the text control selections" section. Let me know if you'd prefer it placed elsewhere as I wasn't sure where the best spot for it was.