Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 947e0ed57ed11d54e8a568748e8cfdc547251ac9
https://github.com/WebKit/WebKit/commit/947e0ed57ed11d54e8a568748e8cfdc547251ac9
Author: Dan Glastonbury <[email protected]>
Date: 2026-07-28 (Tue, 28 Jul 2026)
Changed paths:
A
LayoutTests/fast/block/remove-out-of-flow-child-does-not-affect-anonymous-wrappers-expected.txt
A
LayoutTests/fast/block/remove-out-of-flow-child-does-not-affect-anonymous-wrappers.html
M Source/WebCore/rendering/updating/RenderTreeBuilder.cpp
Log Message:
-----------
Avoid recomputing anonymousWrappers on removal of out-of-flow elements.
https://bugs.webkit.org/show_bug.cgi?id=320142
rdar://183081340
Reviewed by Alan Baradlay.
Since out-of-flow/floating boxes don't participate in the inline/block
determination that creates anonymous wrappers, removing an out-of-flow
positioned or floating child cannot change whether the parent's in-flow children
need their anonymous wrappers.
When removing many absolutely-positioned children from a large container,
removeAnonymousWrappersForInlineChildrenIfNeeded() scans all of the parent's
children, so skipping it for out-of-flow removals avoids O(n) work per removed
child.
* Source/WebCore/rendering/updating/RenderTreeBuilder.cpp:
(WebCore::RenderTreeBuilder::destroyAndCleanUpAnonymousWrappers):
*
LayoutTests/fast/block/remove-out-of-flow-child-does-not-affect-anonymous-wrappers-expected.txt:
Added.
*
LayoutTests/fast/block/remove-out-of-flow-child-does-not-affect-anonymous-wrappers.html:
Added.
Canonical link: https://commits.webkit.org/318113@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
