Branch: refs/heads/webkitglib/2.38
Home: https://github.com/WebKit/WebKit
Commit: 9faa180d9073c1522038144ddb04a62a9e6c6a69
https://github.com/WebKit/WebKit/commit/9faa180d9073c1522038144ddb04a62a9e6c6a69
Author: Tim Nguyen <n...@apple.com>
Date: 2022-12-20 (Tue, 20 Dec 2022)
Changed paths:
M Source/WebCore/rendering/updating/RenderTreeUpdater.cpp
Log Message:
-----------
Cherry-pick 255733@main (394f41a9f855).
https://bugs.webkit.org/show_bug.cgi?id=246735
Don't unnecessarily tear down top layer renderers in RenderTreeUpdater
https://bugs.webkit.org/show_bug.cgi?id=246735
rdar://101324926
Reviewed by Antti Koivisto.
The element.isInTopLayer() check added by
https://commits.webkit.org/246767@main is there is because
entering top layer forces `display: contents` style to `display: block`.
This check is now redundant
with https://commits.webkit.org/255527@main, since it is fixing the same
issue more globally.
Test: fast/css/top-layer-display-contents-crash.html
* Source/WebCore/rendering/updating/RenderTreeUpdater.cpp:
(WebCore::RenderTreeUpdater::updateElementRenderer):
Canonical link: https://commits.webkit.org/255733@main
_______________________________________________
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes
