Re: [whatwg/dom] Candidates for AbstractRange (#591)

> it seems it has to support mutability somewhat

Does it?  Why?

We could have an impl of StaticRange that basically saves values from the ctor and that's it.  cloneRange would still make sense.  so would `start/endContainer/Offset`, `collapsed`, `commonAncestorContainer` (though for a StaticRange this last might need to throw or return null).

`compareBoundaryPoints` would make sense, maybe.  `isPointInRange` might, maybe.  `comparePoint` might, maybe.  `intersectsNode` might, maybe.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/591#issuecomment-372821725

Received on Tuesday, 13 March 2018 21:18:23 UTC