W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2019

[csswg-drafts] [css-highlight-api][css-contain] static ranges and css-contain (#4598)

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Fri, 13 Dec 2019 06:54:45 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-537380700-1576220083-sysbot+gh@w3.org>
frivoal has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-highlight-api][css-contain] static ranges and css-contain ==
The interaction of StaticRanges in a highlight range group and css-contain seems problematic: on a fully contained element, you should expect that DOM changes to descendants of that element will not cause invalidation and restyling/repainting of elements outside the contained one.

However, if a static range has a boundary point inside the contained subtree and another boundary point outside of it, and the DOM in the contained subtree is changed so that the boundary point inside no longer points to a valid node, the whole range should be ignored, which would affect painting outside the contained subtree. Is this a weakness of style containment, or of the invalidation logic in https://drafts.csswg.org/css-highlight-api-1/#range-invalidation, or something else?

Maybe we need to say that static ranges cannot cross the boundary of a contained element, either making it always invalid, or equivalent to a static range starting at its specified starting point, but truncated at the contained element boundary? or something else?

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4598 using your GitHub account
Received on Friday, 13 December 2019 06:54:46 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:31:18 UTC