Re: [whatwg/dom] Add OpaqueRange interface (PR #1404)

@stephanieyzhang commented on this pull request.



> + <li><p>Set <a>this</a>'s <a for=range>end offset</a> to 0.
+</ol>
+</div>
+
+<p>The {{OpaqueRange/getClientRects()}} and {{OpaqueRange/getBoundingClientRect()}} methods are
+defined in [[CSSOM-VIEW]].
+
+<p>An {{OpaqueRange}} is a <a>range</a> whose <a for=range>is opaque</a> flag is true.
+
+<p>An {{Element}}
+<dfn export id=supports-opaque-range>supports opaque ranges</dfn> if its specification defines that
+it does. In HTML, this includes certain {{HTMLInputElement}} types and {{HTMLTextAreaElement}}.
+
+<p class=note>Other specifications can designate additional elements, including custom elements.
+
+<p>An {{OpaqueRange}} is live, meaning its offsets are automatically updated when the underlying

Updated: the tree mutation algorithms now update opaque ranges alongside live range. I kept them separate from "live ranges" to avoid ambiguity in `createRange() / cloneRange()`, but happy to fold them into "live ranges" or introduce a shared umbrella term if you prefer.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/pull/1404#discussion_r4187825207
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/pull/1404/review/5419448588@github.com>