Branch: refs/heads/webkitglib/2.46
  Home:   https://github.com/WebKit/WebKit
  Commit: b85b00257bbaf41e9289e1ca6865ad83534c7124
      
https://github.com/WebKit/WebKit/commit/b85b00257bbaf41e9289e1ca6865ad83534c7124
  Author: Fujii Hironori <hironori.fu...@sony.com>
  Date:   2025-03-04 (Tue, 04 Mar 2025)

  Changed paths:
    M Source/WebKit/UIProcess/skia/BackingStoreSkia.cpp

  Log Message:
  -----------
  Cherry-pick 288818@main (0aed73553051). 
https://bugs.webkit.org/show_bug.cgi?id=285718

    [Skia] ASSERTION FAILED: bitmap->size() == updateSize : 
BackingStore::incorporateUpdate(UpdateInfo &&) on a fractional device scale 
factor display
    https://bugs.webkit.org/show_bug.cgi?id=285718

    Reviewed by Don Olmstead.

    Windows supports fractional device scale factors. For example, 125%,
    150% and 175% DPI display. BackingStore::incorporateUpdate has an
    assertion that checkes a ShareableBitmap size is the bounding rect
    size scaled by the device scale factor. However, this assertion failed
    if the device scale factor was fractional.

    <https://commits.webkit.org/279794@main> added `expandedIntSize` to
    BackingStoreCairo.cpp to solve a same problem. Did the same for
    BackingStoreSkia.cpp.

    * Source/WebKit/UIProcess/skia/BackingStoreSkia.cpp:
    (WebKit::BackingStore::incorporateUpdate):

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

Canonical link: https://commits.webkit.org/282416.463@webkitglib/2.46


  Commit: bebc133af7083b374c5c34c76461c0dae9662d4c
      
https://github.com/WebKit/WebKit/commit/bebc133af7083b374c5c34c76461c0dae9662d4c
  Author: Alex Christensen <achristen...@apple.com>
  Date:   2025-03-04 (Tue, 04 Mar 2025)

  Changed paths:
    M Source/WebCore/dom/Document.cpp

  Log Message:
  -----------
  Cherry-pick 288630@main (c4c4381fdb0f). 
https://bugs.webkit.org/show_bug.cgi?id=285645

    Null check page in Document::nodeWillBeRemoved
    https://bugs.webkit.org/show_bug.cgi?id=285645
    rdar://142586492

    Reviewed by Charlie Wolfe.

    I have a crash log that indicates that it can be null during teardown.

    * Source/WebCore/dom/Document.cpp:
    (WebCore::Document::nodeWillBeRemoved):

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

Canonical link: https://commits.webkit.org/282416.464@webkitglib/2.46


  Commit: f4907c2c934ae4db907ee629f069304d2e158e22
      
https://github.com/WebKit/WebKit/commit/f4907c2c934ae4db907ee629f069304d2e158e22
  Author: Alex Christensen <achristen...@apple.com>
  Date:   2025-03-04 (Tue, 04 Mar 2025)

  Changed paths:
    M Tools/WebKitTestRunner/InjectedBundle/InjectedBundlePage.cpp

  Log Message:
  -----------
  Cherry-pick 288629@main (a0fef0ff952f). 
https://bugs.webkit.org/show_bug.cgi?id=285650

    Add null check in InjectedBundlePage::didClearWindowForFrame
    https://bugs.webkit.org/show_bug.cgi?id=285650
    rdar://142587914

    Reviewed by Charlie Wolfe.

    Crash logs indicate it can be null, especially with site isolation on.

    * Tools/WebKitTestRunner/InjectedBundle/InjectedBundlePage.cpp:
    (WTR::InjectedBundlePage::didClearWindowForFrame):

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

Canonical link: https://commits.webkit.org/282416.465@webkitglib/2.46


Compare: https://github.com/WebKit/WebKit/compare/63851859470d...f4907c2c934a

To unsubscribe from these emails, change your notification settings at 
https://github.com/WebKit/WebKit/settings/notifications
_______________________________________________
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes

Reply via email to