Re: [whatwg/dom] Define criteria for StaticRange validation (#947)

At TPAC 2019 it was discussed that highlight API would internally need to keep basically a live range.
StaticRange would be used just as a way to pass the data about highlight area without keeping (live) Range object alive in JS land
(since live Ranges tend to slow down DOM operations, especially if there are many of them around).
I guess that idea hasn't materialized.

I think keeping the range alive inside highlight API implementation would also solve issue 7 mentioned in the spec.
And issue 7 isn't the only issue StaticRange + validating later approach brings.
It isn't clear to me how StaticRange + validating later can work given all the possible DOM mutations.


-- 
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/947#issuecomment-777350740