[css2] 192 resolution and child issues

--HG--
extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%402544

Author: Hixie

css2/issues/issues-3

@@ -3890,17 +3890,17 @@ Issue 192.
 URI: http://lists.w3.org/Archives/Member/w3c-css-wg/2006JulSep/0049.html
 URI: http://lists.w3.org/Archives/Member/w3c-css-wg/2006JulSep/0157.html
 Description:
-  Appendix E wording (Paragraph starting "for each element in each line
-  box") for painting inlines is not very clear.
+Appendix E wording (Paragraph starting "for each element in each line
+box") for painting inlines is not very clear.
 Proposals:
 Replace
   1. For each element in each line box of the element, in tree order, if
      any, or if the element is inline-level (note that all elements in line
      boxes are forcably inline-level), on a per-line-box basis:
 with
-  1. For each element in each line box of the element (if any), in tree
-     order; or if the element is inline-level (note that all elements in line
-     boxes are forcibly inline-level), on a per-line-box basis:
+� 1. For each element in each line box of the element (if any), in tree
+� � �order; or if the element is inline-level (note that all elements in line
+� � �boxes are forcibly inline-level), on a per-line-box basis:
 or
   1. For each line box of the box (outer loop), and then for each box, in
      tree order, in that line box (inner loop):
@@ -3912,7 +3912,32 @@ or
 
 Resolution:
 
-=WG= Discuss.
+Replace 6, 6.1, and 6.2 with:
+
+6. If the element is an inline element that generates a stacking
+   context, then:
+   1. For each line box that the element is in:
+      1. Jump to 7.2.1 for the box(es) of the element in that line
+         box (in tree order).
+
+7. Otherwise: first for the element, then for all its in-flow,
+   non-positioned, block-level descendants in tree order:
+   1. If the element is a block-level replaced element, then the
+      replaced content, atomically.
+   2. Otherwise, for each line box of that element:
+      1. For each box that is a child of that element, in that line
+         box, in tree order:
+         [current child list of 6.1]
+         Note: Some of the boxes may have been generated by line
+         splitting or the Unicode bidirectional algorithm.
+
+...then change 6.1.4.4.1 to be 7.2.1.4.4.1 and have it read: "Jump
+to step 7.2.1 for the box(es) of this element in this line box."
+
+...then change what used to be 6.1.5 and 6.3 to mention "see 10
+below" instead of "see 9 below".
+
+=Hixie= Edit.
 ------------------------------------------------------------------------
 Issue 193.
 URI: http://lists.w3.org/Archives/Member/w3c-css-wg/2006JulSep/0049.html
@@ -3948,4 +3973,35 @@ outline style is 'none' or 'hidden'". But further down it says
 that 'hidden' is not a legal value for 'outline-style'.
 Proposal:
 Remove "or 'hidden'" from the computed-value line.
+Resolution:
 =WG= Discuss.
+------------------------------------------------------------------------
+Issue 197.
+Description:
+Text of an inline element should be painted in tree order with inline
+descendants.
+Resolution:
+
+Replace 7.2.1.4.3 and 7.2.1.4.4 with:
+
+3. Then for all the element's in-flow, non-positioned, inline-level
+   children, including anonymous inline elements generated for text
+   inside the element, in tree order:
+    1. If the element was generated for text, paint the text.
+    2. Otherwise, jump to 7.1.1. for that element.
+
+=WG= Discuss.
+------------------------------------------------------------------------
+Issue 198.
+Description:
+Appendix E. Replace "Element" with "Segment".
+Resolution:
+=WG= Discuss.
+------------------------------------------------------------------------
+Issue 199.
+Description:
+If a rel pos inline contains a block then the block doesn't move along
+with the rel positioning.
+Resolution:
+=WG= Discuss.
+------------------------------------------------------------------------