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

@smaug---- commented on this pull request.



> @@ -9981,6 +9988,96 @@ and {{Range/getBoundingClientRect()}} methods are defined in other specification
 [[CSSOM-VIEW]]
 
 
+<h3 id=interface-opaquerange>Interface {{OpaqueRange}}</h3>
+
+<pre class=idl>
+[Exposed=Window]
+interface OpaqueRange : AbstractRange {
+  undefined disconnect();
+  DOMRectList getClientRects();
+  DOMRect getBoundingClientRect();
+};
+</pre>
+
+<p>Objects implementing the {{OpaqueRange}} interface are known as {{OpaqueRange}} objects.
+{{OpaqueRange}} objects cannot be constructed directly; they are created by specifications defining

What does creating a `new OpaqueRange(...) `really mean? How would a custom element indicate what kind of value getClientRects as an example should return.

(Hmm, is OpaqueRange kind of a proxy object,  and then there should be the other side of the thing which affects how it behaves. In case of input and textarea, that other side is native and with Custom Elements it would need to be JS based, maybe. Just mumbling aloud.)

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

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