- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Feb 2022 19:20:28 +0000
- To: public-css-archive@w3.org
Sorry for being late to this convo. Unfortunately, @frivoal, I don't think you're right here. Paint containment *does not* ensure that arbitrary changes in the subtree don't result in paint changes outside the subtree, it ensures that *painting originating inside of the subtree* doesn't escape the bounds and require invalidation of a larger area (and lets us avoid having to defensively optimize against such an event with overly-large textures, etc). Various details not related to "doing painting" can absolutely affect what's outside of the subtree and cause it to need to update in various ways, up to and including painting. So in this particular situation, the presence of a range (static or live) intersecting with a paint-contained subtree is definitely outside the set of things covered by that containment. Similarly, none of the other containments would restrict this; it's outside the remit of even style containment. So, I think containment has nothing to say about ranges. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4598#issuecomment-1028277816 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 February 2022 19:20:30 UTC