[webkit-changes] [WebKit/WebKit] c6fb01: RenderLayer::recursiveUpdateLayerPositions() no lo...

[Simon Fraser]

  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: c6fb0168de49b784a40b3f4d9a843dd408ad0869
      https://github.com/WebKit/WebKit/commit/c6fb0168de49b784a40b3f4d9a843dd408ad0869
  Author: Simon Fraser <simon.fraser at apple.com>
  Date:   2023-12-04 (Mon, 04 Dec 2023)

  Changed paths:
    M Source/WebCore/rendering/RenderLayer.cpp
    M Source/WebCore/rendering/RenderLayer.h

  Log Message:
  -----------
  RenderLayer::recursiveUpdateLayerPositions() no longer needs a RenderGeometryMap
https://bugs.webkit.org/show_bug.cgi?id=265821
rdar://119153457

Reviewed by Alan Baradlay.

Now that we no longer call `outlineBoundsForRepaint()` in `RenderLayer::computeRepaintRects()`
we don't need to pass a RenderGeometryMap around, which means that it's more efficient for
`recursiveUpdateLayerPositions()` to just not create and maintain one (the pushing and popping
is not free).

This is a minor progression on some MotionMark subtests.

* Source/WebCore/rendering/RenderLayer.cpp:
(WebCore::RenderLayer::updateLayerPositionsAfterStyleChange):
(WebCore::RenderLayer::updateLayerPositionsAfterLayout):
(WebCore::RenderLayer::recursiveUpdateLayerPositions):
(WebCore::RenderLayer::computeRepaintRects):
(WebCore::RenderLayer::updateLayerPositionsAfterOverflowScroll):
(WebCore::RenderLayer::updateLayerPositionsAfterDocumentScroll):
(WebCore::RenderLayer::recursiveUpdateLayerPositionsAfterScroll):
* Source/WebCore/rendering/RenderLayer.h:
(WebCore::RenderLayer::recursiveUpdateLayerPositionsAfterScroll):

Canonical link: https://commits.webkit.org/271541@main