aboutsummaryrefslogtreecommitdiffstats
path: root/python/servo/win32_toast.py
diff options
context:
space:
mode:
authorBobby Holley <bobbyholley@gmail.com>2016-12-10 20:11:36 -1000
committerBobby Holley <bobbyholley@gmail.com>2016-12-12 18:50:33 -0800
commit3a5695406939dbe370d7cf467d69be7ee6c38759 (patch)
tree18c6c62f57978842442121b662fe243e145b2ed4 /python/servo/win32_toast.py
parent75e4c16bc7e1f50a19f52b095d3327462d9c1459 (diff)
downloadservo-3a5695406939dbe370d7cf467d69be7ee6c38759.tar.gz
servo-3a5695406939dbe370d7cf467d69be7ee6c38759.zip
Bug 1322945 - Change skip_root to unstyled_children_only and use StyleNewChildren in more places. r=heycam
I noticed that our current behavior in ContentRangeInserted is incorrect. Unlike ContentInserted (where this code lived originally), ContentRangeInserted takes a start and end element. I'm not sure if we ever take that path for new content that needs style, but it seemed sketchy. And generally, it seems nice to just always style new content the same way (though we still need to style NAC by the subtree root, since it hasn't been attached to the parent yet). For situations where there is indeed only one unstyled child, the traversal overhead should be neglible, since we special-case the single-element in parallel.rs to avoid calling into rayon. Being more explicit about what we want here also makes us more robust against the other handful of callpaths that can take us into nsCSSFrameConstructor::{ContentRangeInserted,ContentAppended}. Currently we can call StyleNewSubtree on an already-styled element via RecreateFramesForContent, which triggers an assertion in the servo traversal. MozReview-Commit-ID: DqCGh90deHH
Diffstat (limited to 'python/servo/win32_toast.py')
0 files changed, 0 insertions, 0 deletions