@@ -571,37 +571,38 @@ <h2 id=list-style-position-property><span class=secno>4. </span> Marker
571571 in this state, and this ‘< code class =css > ::marker</ code > ’ box
572572 participates in the inline box model in the normal manner.
573573 < p class =issue > Inline markers have some special behavior wrt white-space
574- collapsing at the beginning of the list-item. I need to figure this out
575- and spec it. (Since I have hanging and outside markers be abspos, it
576- doesn't apply to them.)
574+ collapsing at the beginning of the list-item. Is this behavior necessary
575+ for web-compat, or can I just spec it away? (Since I have hanging and
576+ outside markers be abspos, it doesn't apply to them.)
577577
578578 < dt > < dfn id =hanging > hanging</ dfn >
579579
580- < dd > As ‘< a href ="#inside "> < code class =css > inside</ code > </ a > ’,
581- except the marker is absolutely positioned. The marker's static position
582- is such that its baseline is aligned with the baseline of the first line
583- box in the list item, and its "end" edge is flush with the "start" edge
584- of the first line box in the list item. < span class =note > Note that, per
585- the Positioned Layout spec, absolutely positioned boxes leave behind a
586- ‘< code class =property > placeholder</ code > ’ in their original
587- position in the box tree, which may have an effect on line-box
588- generation.</ span >
580+ < dd > As ‘< a href ="#inside "> < code
581+ class =property > inside</ code > </ a > ’, except the marker is instead
582+ placed immediately before the first text or significant whitespace in the
583+ list item or its children. The marker is then absolutely positioned
584+ (leaving behind a placeholder, per the Positioned Layout spec), with the
585+ static position such that the "end" edge of the marker is against the
586+ "start" edge of the placeholder, and the baseline of the marker is
587+ aligned with the placeholder.
588+ < p class =issue > I haven't yet defined what happens when the list item
589+ doesn't contain any text, or when the first text is within a child
590+ list-item. I need to figure out how much of current implementations is
591+ accidental and how much is necessary.
589592
590593 < dt > < dfn id =outside > outside</ dfn >
591594
592- < dd > As ‘< a href ="#inside "> < code class =css > inside</ code > </ a > ’,
593- except the marker is absolutely positioned and has the same
594- directionality as the list item's parent box. The marker's static
595- position is such that its "over" edge is flush with the edge of the list
596- item corresponding with the "over" edge of the list item's parent box,
597- and it's "end" edge is flush with the edge fo the list item corresponding
598- to the "start" edge of the list item's parent box.
595+ < dd > As ‘< a href ="#hanging "> < code
596+ class =css > hanging</ code > </ a > ’, except the horizontal static
597+ position of the marker is such that the marker's "end" edge is placed
598+ against the "start" edge of the list item's parent. < span class =note > The
599+ ‘< a href ="#outside "> < code class =css > outside</ code > </ a > ’ value
600+ has additional implications for the marker, described in the < a
601+ href ="#marker-pseudoelement "> Marker section</ a > .</ span >
602+ < p class =issue > The same problems with ‘< a href ="#hanging "> < code
603+ class =property > hanging</ code > </ a > ’ apply here.
599604 </ dl >
600605
601- < p class =issue > Are the positioning rules for ‘< a
602- href ="#hanging "> < code class =css > hanging</ code > </ a > ’ and ‘< a
603- href ="#outside "> < code class =css > outside</ code > </ a > ’ good?
604-
605606 < p > Note that a marker is only generated if the computed value of the
606607 ‘< code class =property > content</ code > ’ property for the
607608 element's ‘< code class =css > ::marker</ code > ’ pseudo-element is
0 commit comments