Branch: refs/heads/webkitglib/2.52
Home: https://github.com/WebKit/WebKit
Commit: 3a1c80221cdddafab2c042c91e7137c80319a355
https://github.com/WebKit/WebKit/commit/3a1c80221cdddafab2c042c91e7137c80319a355
Author: Fujii Hironori <[email protected]>
Date: 2026-04-07 (Tue, 07 Apr 2026)
Changed paths:
A LayoutTests/scrollbars/zero-height-crash-expected.txt
A LayoutTests/scrollbars/zero-height-crash.html
M Source/WebCore/page/scrolling/coordinated/ScrollerCoordinated.cpp
Log Message:
-----------
Cherry-pick 310503@main (f4f70471df90).
https://bugs.webkit.org/show_bug.cgi?id=311295
[GTK][WPE] assertion failed for empty scrollbar frame rect
https://bugs.webkit.org/show_bug.cgi?id=311295
Reviewed by Nikolas Zimmermann.
If a scrollbar frame rect was empty, the following assertion was failing.
> ASSERTION FAILED: !texture.size().isEmpty()
> ../../../Source/WebCore/platform/graphics/skia/SkiaUtilities.cpp(52) :
GrBackendTexture
WebCore::ScrollerCoordinated::updateValues should return early if the
scrollbar
frame rect is emtpy.
Test: scrollbars/zero-height-crash.html
* LayoutTests/scrollbars/zero-height-crash-expected.txt: Added.
* LayoutTests/scrollbars/zero-height-crash.html: Added.
* Source/WebCore/page/scrolling/coordinated/ScrollerCoordinated.cpp:
(WebCore::ScrollerCoordinated::updateValues):
Canonical link: https://commits.webkit.org/310503@main
Canonical link: https://commits.webkit.org/305877.360@webkitglib/2.52
Commit: c4bce0f6c073f5f693a6de5797f8b2f4ee77b79d
https://github.com/WebKit/WebKit/commit/c4bce0f6c073f5f693a6de5797f8b2f4ee77b79d
Author: Sebastian Krzyszkowiak <[email protected]>
Date: 2026-04-07 (Tue, 07 Apr 2026)
Changed paths:
M Source/WebCore/dom/PointerEvent.h
M Source/WebCore/dom/glib/PointerEventGLib.cpp
M Source/WebCore/page/EventHandler.cpp
M Source/WebCore/platform/PlatformTouchPoint.h
Log Message:
-----------
Cherry-pick 309600@main (e949d0194653).
https://bugs.webkit.org/show_bug.cgi?id=303134
[GTK][WPE] Unify touch Pointer Event handling and make it capture aware
https://bugs.webkit.org/show_bug.cgi?id=303134
Reviewed by Carlos Garcia Campos.
As it is right now, touch Pointer Events in WPE ignore the requirement to
implicitly capture the touch pointer given by the spec, while in GTK they
force
the capture unconditionally. While GTK gives the right behavior by default,
web
content should be able to control pointer capture with
Element::setPointerCapture
and Element::releasePointerCapture API.
Unify the behavior between WPE and GTK ports and make it handle pointer
captures.
Take advantage of the fact that we don't have to perform hit testing while
the pointer remains captured.
Also, remove the injection of pointercancel events in WPE port, as this
behavior
doesn't seem to match anything described in the Pointer Events spec.
* Source/WebCore/dom/PointerEvent.h:
* Source/WebCore/dom/glib/PointerEventGLib.cpp:
(WebCore::PointerEvent::pointerIdForTouchPoint): Expose pointerId mapping
* Source/WebCore/page/EventHandler.cpp:
(WebCore::EventHandler::handleTouchEvent):
* Source/WebCore/platform/PlatformTouchPoint.h:
Canonical link: https://commits.webkit.org/309600@main
Canonical link: https://commits.webkit.org/305877.361@webkitglib/2.52
Commit: 65917ecbed467b2ecc48da16f26b6e894e037261
https://github.com/WebKit/WebKit/commit/65917ecbed467b2ecc48da16f26b6e894e037261
Author: Abrar Rahman Protyasha <[email protected]>
Date: 2026-04-07 (Tue, 07 Apr 2026)
Changed paths:
M Source/WebCore/inspector/agents/InspectorIndexedDBAgent.cpp
Log Message:
-----------
Cherry-pick 310488@main (0125fbadd495).
https://bugs.webkit.org/show_bug.cgi?id=311364
IndexedDB inspection can silently fail when document has no IDB factory
https://bugs.webkit.org/show_bug.cgi?id=311364
rdar://173963020
Reviewed by Megan Gardner and Aditya Keerthi.
In InspectorIndexedDBAgent.cpp, `IDBFactoryFromDocument()` constructs an
error via `makeUnexpected(...)` when `idbFactory` is null, but fails to
actually return it.
This means the error is silently discarded and execution falls through to
the next line, which returns a null idbFactory as a success value.
As a result, when a document has no IndexedDB factory, instead of
propagating a descriptive error back to the Inspector frontend, the agent
returns a null pointer wrapped in a success result, which could cause a
null dereference in callers or silently break IndexedDB inspection.
We discovered this bug during the migration to std::unexpected, because
the standard analogue of that type has a nodiscard constructor.
* Source/WebCore/inspector/agents/InspectorIndexedDBAgent.cpp:
(WebCore::IDBFactoryFromDocument):
Canonical link: https://commits.webkit.org/310488@main
Canonical link: https://commits.webkit.org/305877.362@webkitglib/2.52
Compare: https://github.com/WebKit/WebKit/compare/bc607e9143c6...65917ecbed46
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
