Bug 243859

Summary: REGRESSION (STP 151): List layout broken on CSS3Test.com
Product: WebKit Reporter: Ahmad Saleem <ahmad.saleem792>
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ap, bfulgham, koivisto, rniwa, simon.fraser, webkit-bug-importer, zalan
Priority: P2 Keywords: InRadar
Version: Safari 15   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=243485
Attachments:
Description Flags
Safari 15.6 vs STP 151
none
253353@main no-repro none

Ahmad Saleem
Reported 2022-08-11 16:48:33 PDT
Created attachment 461552 [details] Safari 15.6 vs STP 151 Hi Team, Another website, which has broken layout in STP 151, I don't have reduction test case so please refer to attached screenshot for reference: Link - https://css3test.com EXPECTED RESULT - Should behave same as "Safari 15.6" Thanks
Attachments
Safari 15.6 vs STP 151 (4.45 MB, image/png)
2022-08-11 16:48 PDT, Ahmad Saleem 		no flags
Details
253353@main no-repro (2.69 MB, image/png)
2022-08-11 19:02 PDT, alan 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2022-08-11 18:24:35 PDT
<rdar://problem/98541640>
alan
Comment 2 2022-08-11 19:02:17 PDT
Created attachment 461553 [details] 253353@main no-repro I can't repro it with 253353@main (ToT)
Alexey Proskuryakov
Comment 3 2022-08-12 09:22:47 PDT
I can reproduce with STP 151, but not with a recent macOS Ventura build, nor with STP 150.
Ahmad Saleem
Comment 4 2022-08-29 06:38:18 PDT
This does not reproduce in STP 152, any idea which commit fixed it?
Ahmad Saleem
Comment 5 2022-08-29 09:18:54 PDT
It was not reproducible by @zalan in the ToT as per Comment 02 and it is also not reproducible in STP 152. I am going to mark this as "RESOLVED CONFIGURATION CHANGED". If someone can post, which commit fixed it, it would be great for future purposes. Thanks!
alan
Comment 6 2022-08-29 09:26:24 PDT
progressed at 253079@main
Note You need to log in before you can comment on or make changes to this bug.