Re: [whatwg/dom] Add validity criteria for StaticRange (#1009)

Use of StaticRanges forces one to use MutationObserver or other mechanisms to detect mutations in order to keep StaticRanges up-to-date all the time, so the tests were very much unrealistic.
(Also, live Ranges need to observe changes only in the subtree they live in
"The Document stores a collection of pointers to all the Ranges that are alive inside it.
Whenever there’s a DOM mutation that involves deletion/addition of nodes or text for example, all these Ranges are notified about the mutation." smells like some implementations have rather heavyweight Ranges, but that is an implementation detail.)

 But anyhow, this change as such is fine.

-- 
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/pull/1009#issuecomment-909025963