Bug 252092 - Some tests with extreme border radius regressed in WebKit ToT
Summary: Some tests with extreme border radius regressed in WebKit ToT
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: Safari Technology Preview
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: BrowserCompat, InRadar
Depends on:
Blocks:
 
Reported: 2023-02-10 16:42 PST by Ahmad Saleem
Modified: 2023-02-22 15:42 PST (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ahmad Saleem 2023-02-10 16:42:20 PST
Hi Team,

While trying to test the blink commit modifying some code around comment in Source Code referring bug 38787, I curiously tested the test case and noted that WebKit ToT 260132@main (tested using minibrowser --release) has regressed them compare to Firefox Nightly 111 and Chrome Canary 112 and Safari 16.3:

Test Case - https://bug-38787-attachments.webkit.org/attachment.cgi?id=89989

^ Safari 16.3 is broke compared to Chrome Canary 112 and Firefox Nightly 111. Both Chrome and Firefox Nightly match each other.

Test Case - https://bug-38787-attachments.webkit.org/attachment.cgi?id=110436

^ Safari 16.3 matches with Chrome Canary 112 and Firefox Nightly 111 but WebKit ToT differs.

WebKit ToT is matching Safari Technology Preview 163, so this can be tested in STP as well.

Just wanted to raise so this can be tracked and fixed.
Comment 1 Ahmad Saleem 2023-02-10 16:43:05 PST
For curious - I was looking into this Blink Commit - https://chromium.googlesource.com/chromium/blink/+/bad16564c8238c305bc8035da0b5cfcda0a644c6
Comment 2 Radar WebKit Bug Importer 2023-02-13 10:08:12 PST
<rdar://problem/105402068>
Comment 3 Ahmad Saleem 2023-02-22 15:42:10 PST
So it seems that the regression is between Safari Technology Preview 163 & 164. Just tested and matching with WebKit ToT where I identified these failures.