243664 2022-08-08 05:41:31 -0700 REGRESSION(248294@main): wpt /css/CSS2/lists/list-style-position-018.xht 2023-10-30 09:56:28 -0700 1 1 1 Unclassified WebKit Layout and Rendering WebKit Nightly Build Unspecified Unspecified RESOLVED CONFIGURATION CHANGED https://bugs.webkit.org/show_bug.cgi?id=237497 https://bugs.webkit.org/show_bug.cgi?id=243303 https://bugs.webkit.org/show_bug.cgi?id=209735 InRadar P2 Normal --- 1 gsnedders webkit-unassigned ahmad.saleem792 bfulgham simon.fraser webkit-bug-importer zalan oldest_to_newest 1889652 0 gsnedders 2022-08-08 05:41:31 -0700 I think this is quite possibly the same as "^^progressions. Align list marker with the content (like Firefox does)." in the commit message, but someone (Alan) should check. If it is, we should change the test and/or the spec. 1889653 1 webkit-bug-importer 2022-08-08 05:41:42 -0700 <rdar://problem/98313910> 1889708 2 zalan 2022-08-08 10:40:13 -0700 Yeah, your are correct, it is the same. I don't have a strong preference on this (especially as it's an "outside" marker, which is remarkably quirky) but it just felt right to have it aligned with FF (and the existing inline layout logic kinda leaned towards this solution) 1890417 3 zalan 2022-08-10 15:10:10 -0700 While the CSS spec is certainly handwavey here (even https://www.w3.org/TR/css-lists-3/#marker admits so), I think it is rather clear that the marker box and the principal box of the list item are 2 distinct boxes (and possibly formatting contexts) and therefore the marker should not move with the aligned inline content. Will fix. 1890576 4 gsnedders 2022-08-11 07:22:55 -0700 see also https://bugzilla.mozilla.org/show_bug.cgi?id=1750135 re: the Firefox behaviour 1896524 5 zalan 2022-09-06 10:34:14 -0700 This looks to have progressed at 252988@main. 1932463 6 ahmad.saleem792 2023-02-09 14:26:11 -0800 This is passing now: https://wpt.fyi/results/css/CSS2/lists/list-style-position-018.xht?label=master&label=experimental&aligned&view=subtest&q=list-style-position-018.xht Do e need to track it further or we can mark this as 'RESOLVED CONFIGURATION CHANGED' or duplicate of bug 243303 based on Alan's comment? 1932540 7 zalan 2023-02-09 20:30:51 -0800 Thank you!