Branch: refs/heads/webkitglib/2.52
Home: https://github.com/WebKit/WebKit
Commit: e1e325c02cbe8ea6539caee41da10c69299adff7
https://github.com/WebKit/WebKit/commit/e1e325c02cbe8ea6539caee41da10c69299adff7
Author: Fujii Hironori <[email protected]>
Date: 2026-02-09 (Mon, 09 Feb 2026)
Changed paths:
M
Source/WebCore/platform/graphics/texmap/coordinated/CoordinatedBackingStoreProxy.cpp
M
Source/WebCore/platform/graphics/texmap/coordinated/CoordinatedBackingStoreProxy.h
M
Source/WebCore/platform/graphics/texmap/coordinated/CoordinatedPlatformLayer.cpp
Log Message:
-----------
Cherry-pick 306987@main (c898f5980bec).
https://bugs.webkit.org/show_bug.cgi?id=305441
[GTK][WPE][Coordinated Graphics] The combination of damage tracking and
async scrolling causes flickering
https://bugs.webkit.org/show_bug.cgi?id=305441
Reviewed by Carlos Garcia Campos.
The damage tracking tracks the area that is actually drawn, and updates only
the painted area.
If async scrolling scrolled to the area no tiles were covered while the main
thread was busy, new tiles would be created and drawn after the main thread
was
unblocked. However, the area was not recorded as the damage area.
Changed CoordinatedPlatformLayer::updateBackingStore() to collect the area
where new tiles are created, and add to the damage area.
Co-authored-by: Pawel Lampe <[email protected]>
*
Source/WebCore/platform/graphics/texmap/coordinated/CoordinatedBackingStoreProxy.cpp:
(WebCore::CoordinatedBackingStoreProxy::updateIfNeeded):
(WebCore::CoordinatedBackingStoreProxy::createOrDestroyTiles):
*
Source/WebCore/platform/graphics/texmap/coordinated/CoordinatedBackingStoreProxy.h:
*
Source/WebCore/platform/graphics/texmap/coordinated/CoordinatedPlatformLayer.cpp:
(WebCore::CoordinatedPlatformLayer::updateBackingStore):
Canonical link: https://commits.webkit.org/306987@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
