252092 2023-02-10 16:42:20 -0800 Some tests with extreme border radius regressed in WebKit ToT 2024-08-24 11:50:09 -0700 1 1 1 Unclassified WebKit Layout and Rendering Safari Technology Preview Unspecified Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=244638 https://bugs.webkit.org/show_bug.cgi?id=278606 BrowserCompat, InRadar P2 Normal --- 1 ahmad.saleem792 webkit-unassigned bfulgham karlcow simon.fraser vitor.roriz webkit-bug-importer zalan oldest_to_newest 1932822 0 ahmad.saleem792 2023-02-10 16:42:20 -0800 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. 1932823 1 ahmad.saleem792 2023-02-10 16:43:05 -0800 For curious - I was looking into this Blink Commit - https://chromium.googlesource.com/chromium/blink/+/bad16564c8238c305bc8035da0b5cfcda0a644c6 1933220 2 webkit-bug-importer 2023-02-13 10:08:12 -0800 <rdar://problem/105402068> 1935996 3 ahmad.saleem792 2023-02-22 15:42:10 -0800 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. 2055137 4 simon.fraser 2024-08-24 11:46:49 -0700 Probably regressed by bug 244638.