Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 15dbc5a83d163fe4c3d7be4cdd2d3756a4133e18
https://github.com/WebKit/WebKit/commit/15dbc5a83d163fe4c3d7be4cdd2d3756a4133e18
Author: lilly <[email protected]>
Date: 2026-07-15 (Wed, 15 Jul 2026)
Changed paths:
M Source/WebCore/rendering/BorderShape.cpp
Log Message:
-----------
corner-shape: add early return for when there is no startInset or endInset
https://bugs.webkit.org/show_bug.cgi?id=319421
rdar://182245613
Reviewed by Simon Fraser.
per the "compute a contoured path" algorithm in CSS Borders 4 (ยง3.9.4.2,
adjustedRadius), the opposite-corner scale factor is only applied when a
corner has a positive inset (i.e. the inner contours). When both of a
corner's insets are zero, the outer contour adjustedRadius returns the
radius unscaled. Since buildScaledCornerInputs() is also the code path
for the outer contour (addOuterCornerShapeToPath calls it with zero insets),
scaling it unconditionally would shrink the outer border radius along with
the inner one, which is not what the spec specifies. Also update
addOuterCornerShapeToPath()
to build the outer contour directly with buildCornerInputs() instead of
buildScaledCornerInputs(), since with the early-out above the latter would
only compute and discard the scalefactor for the outer contour.
New tests are uneccesary for this change
* Source/WebCore/rendering/BorderShape.cpp:
(WebCore::buildScaledCornerInputs):
(WebCore::addOuterCornerShapeToPath):
Canonical link: https://commits.webkit.org/317245@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
