Branch: refs/heads/webkitglib/2.54
  Home:   https://github.com/WebKit/WebKit
  Commit: bafe814fcf350fe238f9dfe25d47fbf8e604e7e9
      
https://github.com/WebKit/WebKit/commit/bafe814fcf350fe238f9dfe25d47fbf8e604e7e9
  Author: Fujii Hironori <[email protected]>
  Date:   2026-09-28 (Mon, 28 Sep 2026)

  Changed paths:
    M 
Source/WebCore/page/scrolling/coordinated/ScrollingTreeScrollingNodeDelegateCoordinated.cpp
    M 
Source/WebCore/page/scrolling/coordinated/ScrollingTreeScrollingNodeDelegateCoordinated.h
    M Source/WebKit/UIProcess/API/gtk/WebKitWebViewBase.cpp
    M Source/WebKit/WPEPlatform/wpe/WPEGestureDetector.cpp

  Log Message:
  -----------
  Cherry-pick 320147@main (13cc83ffe56b). 
https://bugs.webkit.org/show_bug.cgi?id=321908

    REGRESSION(309315@main): [WPE][GTK] position:fixed layers are unnecessarily 
repainted by scrolling
    https://bugs.webkit.org/show_bug.cgi?id=321908

    Reviewed by Carlos Garcia Campos.

    After 309315@main stopped rounding the scroll position of layers,
    viewport-constrained layers are unnecessarily repainted while scrolling.

    LocalFrameView::updateLayoutViewport has this condition:

    >    if (newLayoutViewportOrigin != m_layoutViewportOrigin) {
    >        setBaseLayoutViewportOrigin(newLayoutViewportOrigin);

    m_layoutViewportOrigin of LocalFrameView is a LayoutPoint, but
    newLayoutViewportOrigin comes from ScrollView::m_scrollPosition, which is
    an IntPoint and thus already rounded. As a result, whenever the scroll
    position had a fractional part, this condition was true and triggered an
    unnecessary layout.

    309315@main solved a problem of accumulated rounding error for touch gesture
    scrolling <https://webkit.org/b/309252>. This can be solved in UI process.
    Reverted 309315@main, and rounded the touch event positions to calculate
    deltas.

    * 
Source/WebCore/page/scrolling/coordinated/ScrollingTreeScrollingNodeDelegateCoordinated.cpp:
    
(WebCore::ScrollingTreeScrollingNodeDelegateCoordinated::adjustedScrollPosition 
const): Deleted.
    * 
Source/WebCore/page/scrolling/coordinated/ScrollingTreeScrollingNodeDelegateCoordinated.h:
    * Source/WebKit/WPEPlatform/wpe/WPEGestureDetector.cpp:
    (WPE::GestureDetector::handleEvent):
    * Source/WebKit/UIProcess/API/gtk/WebKitWebViewBase.cpp:
    (webkitWebViewBaseTouchDragUpdate):

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

Canonical link: https://commits.webkit.org/317695.356@webkitglib/2.54


  Commit: 95911e9b8f8b893ba853c6578548410a1a6c4d59
      
https://github.com/WebKit/WebKit/commit/95911e9b8f8b893ba853c6578548410a1a6c4d59
  Author: Claudio Saavedra <[email protected]>
  Date:   2026-09-28 (Mon, 28 Sep 2026)

  Changed paths:
    M Tools/Scripts/libraries/webkitscmpy/webkitscmpy/program/branch.py
    M 
Tools/Scripts/libraries/webkitscmpy/webkitscmpy/test/pull_request_unittest.py

  Log Message:
  -----------
  Cherry-pick 321879@main (8bb663b39cb8). 
https://bugs.webkit.org/show_bug.cgi?id=323221

    [git-webkit] 'pr --no-bug' does not use the prompted title in the commit 
message
    https://bugs.webkit.org/show_bug.cgi?id=323221

    Reviewed by Patrick Griffis.

    With --no-bug the text entered at the prompt only ever became the branch
    name. args._title is assigned from a resolved issue, and the path that
    would otherwise consume the raw input creates an issue, which --no-bug
    disables. COMMIT_MESSAGE_TITLE was left unset, so the commit message kept
    the placeholder short description that prepare-commit-msg falls back to.

    Keep the input as the commit title when no issue is involved, reusing the
    existing heuristic that a string containing a space is a title rather than
    a branch name. The title is written to branch.<branch>.title, so amends and
    the pull request title pick it up too.

    * Tools/Scripts/libraries/webkitscmpy/webkitscmpy/program/branch.py:
    (Branch.ensure_issue):
    * 
Tools/Scripts/libraries/webkitscmpy/webkitscmpy/test/pull_request_unittest.py:

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

Canonical link: https://commits.webkit.org/317695.357@webkitglib/2.54


  Commit: 4e711fbb9814440f5fc0c5b3d3ba8a1412dc5d14
      
https://github.com/WebKit/WebKit/commit/4e711fbb9814440f5fc0c5b3d3ba8a1412dc5d14
  Author: Carlos Garcia Campos <[email protected]>
  Date:   2026-09-28 (Mon, 28 Sep 2026)

  Changed paths:
    M Source/WebCore/platform/graphics/skia/SkiaBackingStore.cpp
    M 
Source/WebCore/platform/graphics/texmap/coordinated/CoordinatedTileBuffer.h

  Log Message:
  -----------
  Cherry-pick 321685@main (1f44ac925374). 
https://bugs.webkit.org/show_bug.cgi?id=323049

    [GTK] Debug layout tests crash randomly in Skia GrResourceCache: 
skgpu::SingleOwner assert on the SkiaCPUWorker thread
    https://bugs.webkit.org/show_bug.cgi?id=323049

    Reviewed by Nikolas Zimmermann.

    Rename CoordinatedAcceleratedTileBuffer::displayList() as
    takeDisplayList() to transfer the ownership to the caller. This way we
    ensure that if the DDL is replayed then it's also released in the
    compositing thread.

    * LayoutTests/platform/gtk/TestExpectations:
    * Source/WebCore/platform/graphics/coordinated/CoordinatedTileBuffer.h:
    * Source/WebCore/platform/graphics/skia/SkiaBackingStore.cpp:
    (WebCore::SkiaBackingStore::Tile::update):

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

Canonical link: https://commits.webkit.org/317695.358@webkitglib/2.54


Compare: https://github.com/WebKit/WebKit/compare/3948812ba4ed...4e711fbb9814

To unsubscribe from these emails, change your notification settings at 
https://github.com/WebKit/WebKit/settings/notifications

Reply via email to