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

Issue 7 (discussed here: https://github.com/w3c/csswg-drafts/issues/4598) is an additional validation criterion specific to highlights. If we resolve to not support that scenario, before painting a highlight, we need to ensure that the backing StaticRange is valid and that this additional criterion is met. Issue 7 should not generally apply to StaticRange, and the validity checks I am proposing are a generic set of checks that should apply to static ranges in all cases.

As another (hypothetical) example, imagine if a UA/author wanted to implement StaticRange.toString. The API would first need to check if the static range is valid. If it isn't, toString should throw an error or perhaps just return an empty string. If it is valid, then it may return a result in a manner similar to Range.toString.

-- 
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-777705772