- From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 19 May 2011 18:16:15 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-lists
In directory hutz:/tmp/cvs-serv10248
Modified Files:
Overview.html Overview.src.html
Log Message:
Updated 'hanging' and 'outside' positioning rules to better match browsers. They're still not perfect, but I have some issues logged.
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-lists/Overview.html,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -d -r1.41 -r1.42
--- Overview.html 19 May 2011 17:18:27 -0000 1.41
+++ Overview.html 19 May 2011 18:16:13 -0000 1.42
@@ -571,37 +571,38 @@
in this state, and this ‘<code class=css>::marker</code>’ box
participates in the inline box model in the normal manner.
<p class=issue>Inline markers have some special behavior wrt white-space
- collapsing at the beginning of the list-item. I need to figure this out
- and spec it. (Since I have hanging and outside markers be abspos, it
- doesn't apply to them.)
+ collapsing at the beginning of the list-item. Is this behavior necessary
+ for web-compat, or can I just spec it away? (Since I have hanging and
+ outside markers be abspos, it doesn't apply to them.)
<dt><dfn id=hanging>hanging</dfn>
- <dd>As ‘<a href="#inside"><code class=css>inside</code></a>’,
- except the marker is absolutely positioned. The marker's static position
- is such that its baseline is aligned with the baseline of the first line
- box in the list item, and its "end" edge is flush with the "start" edge
- of the first line box in the list item. <span class=note>Note that, per
- the Positioned Layout spec, absolutely positioned boxes leave behind a
- ‘<code class=property>placeholder</code>’ in their original
- position in the box tree, which may have an effect on line-box
- generation.</span>
+ <dd>As ‘<a href="#inside"><code
+ class=property>inside</code></a>’, except the marker is instead
+ placed immediately before the first text or significant whitespace in the
+ list item or its children. The marker is then absolutely positioned
+ (leaving behind a placeholder, per the Positioned Layout spec), with the
+ static position such that the "end" edge of the marker is against the
+ "start" edge of the placeholder, and the baseline of the marker is
+ aligned with the placeholder.
+ <p class=issue>I haven't yet defined what happens when the list item
+ doesn't contain any text, or when the first text is within a child
+ list-item. I need to figure out how much of current implementations is
+ accidental and how much is necessary.
<dt><dfn id=outside>outside</dfn>
- <dd>As ‘<a href="#inside"><code class=css>inside</code></a>’,
- except the marker is absolutely positioned and has the same
- directionality as the list item's parent box. The marker's static
- position is such that its "over" edge is flush with the edge of the list
- item corresponding with the "over" edge of the list item's parent box,
- and it's "end" edge is flush with the edge fo the list item corresponding
- to the "start" edge of the list item's parent box.
+ <dd>As ‘<a href="#hanging"><code
+ class=css>hanging</code></a>’, except the horizontal static
+ position of the marker is such that the marker's "end" edge is placed
+ against the "start" edge of the list item's parent. <span class=note>The
+ ‘<a href="#outside"><code class=css>outside</code></a>’ value
+ has additional implications for the marker, described in the <a
+ href="#marker-pseudoelement">Marker section</a>.</span>
+ <p class=issue>The same problems with ‘<a href="#hanging"><code
+ class=property>hanging</code></a>’ apply here.
</dl>
- <p class=issue>Are the positioning rules for ‘<a
- href="#hanging"><code class=css>hanging</code></a>’ and ‘<a
- href="#outside"><code class=css>outside</code></a>’ good?
-
<p>Note that a marker is only generated if the computed value of the
‘<code class=property>content</code>’ property for the
element's ‘<code class=css>::marker</code>’ pseudo-element is
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-lists/Overview.src.html,v
retrieving revision 1.82
retrieving revision 1.83
diff -u -d -r1.82 -r1.83
--- Overview.src.html 19 May 2011 17:18:27 -0000 1.82
+++ Overview.src.html 19 May 2011 18:16:13 -0000 1.83
@@ -300,30 +300,28 @@
to the ''::marker'' pseudo-element in this state, and this ''::marker'' box
participates in the inline box model in the normal manner.
<p class=issue>Inline markers have some special behavior wrt white-space
- collapsing at the beginning of the list-item. I need to figure this out
- and spec it. (Since I have hanging and outside markers be abspos, it
+ collapsing at the beginning of the list-item. Is this behavior necessary for web-compat,
+ or can I just spec it away? (Since I have hanging and outside markers be abspos, it
doesn't apply to them.)</p></dd>
<dt><dfn>hanging</dfn></dt>
- <dd>As ''inside'', except the marker is absolutely positioned. The marker's
- static position is such that its baseline is aligned with the baseline
- of the first line box in the list item, and its "end" edge is flush with
- the "start" edge of the first line box in the list item.
- <span class=note>Note that, per the Positioned Layout spec, absolutely positioned
- boxes leave behind a 'placeholder' in their original position in the box tree,
- which may have an effect on line-box generation.</span></dd>
+ <dd>As 'inside', except the marker is instead placed immediately before the first
+ text or significant whitespace in the list item or its children. The marker is then
+ absolutely positioned (leaving behind a placeholder, per the Positioned Layout spec),
+ with the static position such that the "end" edge of the marker is against the "start"
+ edge of the placeholder, and the baseline of the marker is aligned with the placeholder.
+ <p class=issue>I haven't yet defined what happens when the list item doesn't contain
+ any text, or when the first text is within a child list-item. I need to figure out how much
+ of current implementations is accidental and how much is necessary.</p></dd>
<dt><dfn>outside</dfn></dt>
- <dd>As ''inside'', except the marker is absolutely positioned and has the same
- directionality as the list item's parent box. The marker's static position is such that
- its "over" edge is flush with the edge of the list item corresponding with
- the "over" edge of the list item's parent box, and it's "end" edge is
- flush with the edge fo the list item corresponding to the "start" edge of the
- list item's parent box.</dd>
+ <dd>As ''hanging'', except the horizontal static position of the marker is such that
+ the marker's "end" edge is placed against the "start" edge of the list item's parent.
+ <span class='note'>The ''outside'' value has additional implications for the marker,
+ described in the <a href="#marker-pseudoelement">Marker section</a>.</span>
+ <p class=issue>The same problems with 'hanging' apply here.</p></dd>
</dl>
- <p class=issue>Are the positioning rules for ''hanging'' and ''outside'' good?</p>
-
<p>Note that a marker is only generated if the computed value of the 'content'
property for the element's ''::marker'' pseudo-element is not ''none''.</p>
Received on Thursday, 19 May 2011 18:16:17 UTC