Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: 8fafd9511671ba8d5e5aa08bf850404746b3b0a3
      
https://github.com/WebKit/WebKit/commit/8fafd9511671ba8d5e5aa08bf850404746b3b0a3
  Author: Ahmad Saleem <ahmad.saleem792+git...@gmail.com>
  Date:   2025-03-04 (Tue, 04 Mar 2025)

  Changed paths:
    A 
LayoutTests/fast/css-intrinsic-dimensions/resize-inside-percent-width-overflow-hidden-expected.txt
    A 
LayoutTests/fast/css-intrinsic-dimensions/resize-inside-percent-width-overflow-hidden.html
    M Source/WebCore/rendering/RenderObject.cpp

  Log Message:
  -----------
  Percent-width blocks cannot form a re-layout boundary

https://bugs.webkit.org/show_bug.cgi?id=247913
rdar://102577429

Reviewed by Alan Baradlay.

This patch is to align Webkit behavior with Blink / Chromium and Gecko / 
Firefox.

Inspired by (+ Tests): 
https://chromium.googlesource.com/chromium/src.git/+/da179e152dff0ab3e3dabc72299bd4fb586881c9

A block with non-visible overflow can only form a re-layout boundary if both
width and height are fixed.

The block may be inside a shrink-to-fit container (there's no cheap and
reliable way to detect that), so that changes inside it may affect its width.

Instead of `isFixed()` checks done in 256901@main, this patch adds missing
check of `width` being PercentOrCalculated.

* Source/WebCore/rendering/RenderObject.cpp:
(WebCore::objectIsRelayoutBoundary):
of relayout for non-fixed container
* 
LayoutTests/fast/css-intrinsic-dimension/resize-inside-percent-width-overflow-hidden.html:
 Added Test Case
* 
LayoutTests/fast/css-intrinsic-dimension/resize-inside-percent-width-overflow-hidden-expected.txt:
 Added Test Case Expectations

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



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