Bug 243664
Summary: | REGRESSION(248294@main): wpt /css/CSS2/lists/list-style-position-018.xht | ||
---|---|---|---|
Product: | WebKit | Reporter: | Sam Sneddon [:gsnedders] <gsnedders> |
Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED CONFIGURATION CHANGED | ||
Severity: | Normal | CC: | ahmad.saleem792, bfulgham, simon.fraser, webkit-bug-importer, zalan |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: |
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 |
Sam Sneddon [:gsnedders]
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.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/98313910>
alan baradlay
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)
alan baradlay
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.
Sam Sneddon [:gsnedders]
see also https://bugzilla.mozilla.org/show_bug.cgi?id=1750135 re: the Firefox behaviour
alan baradlay
This looks to have progressed at 252988@main.
Ahmad Saleem
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?
alan baradlay
Thank you!