Bug 252092
Summary: | Some tests with extreme border radius regressed in WebKit ToT | ||
---|---|---|---|
Product: | WebKit | Reporter: | Ahmad Saleem <ahmad.saleem792> |
Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW | ||
Severity: | Normal | CC: | bfulgham, karlcow, simon.fraser, vitor.roriz, webkit-bug-importer, zalan |
Priority: | P2 | Keywords: | BrowserCompat, InRadar |
Version: | Safari Technology Preview | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: |
https://bugs.webkit.org/show_bug.cgi?id=244638 https://bugs.webkit.org/show_bug.cgi?id=278606 |
Ahmad Saleem
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.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Ahmad Saleem
For curious - I was looking into this Blink Commit - https://chromium.googlesource.com/chromium/blink/+/bad16564c8238c305bc8035da0b5cfcda0a644c6
Radar WebKit Bug Importer
<rdar://problem/105402068>
Ahmad Saleem
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.
Simon Fraser (smfr)
Probably regressed by bug 244638.