[css2] sync to reality

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

Author: Hixie

css2/issues/issues-3

@@ -1590,8 +1590,29 @@ of the section).
 
 -David
 
-=David= Propose changes.
-=WG= Discuss again once dbaron has sent changes.
+Resolution:
+
+ 1. Remove the paragraph:
+
+    # Counters that are not in the scope of any 'counter-reset', are
+    # assumed to have been reset to 0 by a 'counter-reset' on the root
+    # element. 
+
+ 2. Take the sentence at the end of the second paragraph:
+
+    # See "Nested counters and scope" in the chapter on generated
+    # content.
+
+    and make it its own paragraph (i.e., the third), and add to the end
+    so that it reads:
+
+    # See "Nested counters and scope" in the chapter on generated
+    # content for how user agents must determine the value or values of
+    # the counter. See the definition of counter values of the
+    # <a>'content' property</a> for how it must convert these values to
+    # a string.
+
+=howcome= Edit.
 ------------------------------------------------------------------------
 Issue 76.
 URI: http://www.w3.org/mid/42DFD435.7070702@mit.edu
@@ -2214,7 +2235,24 @@ Paul Nelson: http://www.w3.org/mid/49C257E2C13F584790B2E302E021B6F90ED3DF69@wins
 Howcome: http://www.w3.org/mid/17385.2325.554019.960121@localhost.localdomain
 Ian: http://www.w3.org/mid/Pine.LNX.4.62.0602141911330.28514@dhalsim.dreamhost.com
 
-=WG= Discuss.
+
+Resolution:
+
+>   The 'ex' unit is defined by the element's first available font. The
+>   x-height is so called because it is often equal to the height of the
+>   lowercase "x". However, an 'ex' is defined even for fonts that don't
+>   contain an "x".
+> 
+>   The x-height of a font can be found in different ways. Some
+>   fonts contain reliable metrics for the x-height. If reliable font
+>   metrics are not available, UAs may determine the x-height from the
+>   height of a lowercase glyph. One possible heuristics is to look at how
+>   far the glyph for the lowercase "o" extends below the baseline, and
+>   subtract that value from the top of its bounding box. In the cases
+>   where it is impossible or impractical to determine the x-height, a
+>   value of 0.5em should be used. 
+
+=howcome= Edit.
 ------------------------------------------------------------------------
 Issue 96.
 URI: http://www.w3.org/mid/430B4766.8070004@tu-clausthal.de
@@ -2882,15 +2920,12 @@ pre-wrap issue. Last e-mail has proposals.
 Various proposals have been made that differ from the above proposals,
 but they have received push-back.
 
-Suggestion:
-
-Add the following to the second list in 16.6.1:
+Resolution:
 
- 4. If a space (U+0020) at the end of a line has 'white-space' set to
-    'pre-wrap', UAs may remove or may partially truncate the space in
-    an effort to prevent invisible overflow.
+6. If spaces (U+0020) or tabs (U+0009) at the end of a line have
+'white-space' set to 'pre-wrap', UAs may visually collapse them.
 
-=WG= Discuss.
+=Tantek= Edit.
 ------------------------------------------------------------------------
 Issue 141.
 URI: http://www.w3.org/mid/4383ABE2.5010905@mit.edu
@@ -2929,7 +2964,37 @@ Change the start of (4) from "Finally, sort by order specified: if two
 rules have the same weight, origin and specificity," to "Finally, if the
 previous sort still resulted in a tie,".
 
-=WG= Discuss.
+David also proposed:
+
+Choose the declarations at the highest numerical value in the
+following list based on importance (normal or important) and origin
+(author, user, or user agent):
+
+   1. user agent style sheets
+   2. user normal style sheets
+   3. author normal style sheets
+   4. author important style sheets
+   5. user important style sheets
+
+If this results in more than one declaration, choose the
+declarations tied for the highest specificity of selector.
+Pseudo-elements and pseudo-classes are counted as normal elements and
+classes, respectively.
+
+If this results in more than one declaration, break the tie with
+order:  the latter specified wins. Rules in imported style sheets are
+considered to be before any rules in the style sheet itself.
+
+
+Resolution:
+
+Replace 2 with "2. Sort according to importance (normal or important)
+and origin (author, user, or user agent). In ascending order of
+precendence:"
+
+Insert "rules with the same importance and origin" after "3. Sort"
+
+=howcome= Edit.
 ------------------------------------------------------------------------
 Issue 142.
 URI: http://www.w3.org/mid/20051123002259.GA27719@ridley.dbaron.org
@@ -3076,11 +3141,80 @@ And the styles
   #outer { overflow: auto; height: 200px; width: 200px;}
   #inner { height: 100%; width: 200%; }
 
-Now the "outer" div overflows horizontally, so a horizontal scrollbar has to be inserted.  Given that, what is the computed value of "height" for the outer div?  Is
-it 100px?  Or is it (100px - 'height of scrollbar')?  And more specifically, what is the computed value of "height" for the inner div?
+Now the "outer" div overflows horizontally, so a horizontal scrollbar
+has to be inserted.  Given that, what is the computed value of
+"height" for the outer div?  Is it 100px?  Or is it (100px - 'height
+of scrollbar')?  And more specifically, what is the computed value of
+"height" for the inner div?
 
 Resolution:
-=WG= Discuss.
+
+The computed value of the outer 'height' is 200px.
+The computed value of the inner 'height' is 100%.
+
+Proposal:
+
+10.3.3: Change 
+
+   'margin-left' + 'border-left-width' + 'padding-left' + 'width' +
+   'padding-right' + 'border-right-width' + 'margin-right' = width of
+   containing block
+
+   If 'width' is not 'auto' and 'border-left-width' + 'padding-left' +
+   'width' + 'padding-right' + 'border-right-width'
+
+...to:
+
+   'margin-left' + 'border-left-width' + 'padding-left' + 'width' +
+   'padding-right' + 'border-right-width' + 'margin-right' + scrollbar
+   width (if any) = width of containing block
+
+   If 'width' is not 'auto' and 'border-left-width' + 'padding-left' +
+   'width' + 'padding-right' + 'border-right-width' + scrollbar width
+   (if any)
+
+Add to the end of that section:
+
+   The "scrollbar width" value is only relevant if the user agent uses
+   a scrollbar as its scrolling mechanism. See the definition of the
+   'overflow' property.
+
+10.3.7: Change:
+
+   'left' + 'margin-left' + 'border-left-width' + 'padding-left' +
+   'width' + 'padding-right' + 'border-right-width' + 'margin-right' +
+   'right' = width of containing block
+
+...to:
+
+   'left' + 'margin-left' + 'border-left-width' + 'padding-left' +
+   'width' + 'padding-right' + 'border-right-width' + 'margin-right' +
+   'right' + scrollbar width (if any) = width of containing block
+
+Add to the end of that section:
+
+   The "scrollbar width" value is only relevant if the user agent uses
+   a scrollbar as its scrolling mechanism. See the definition of the
+   'overflow' property.
+
+10.6.4: (tbd...)
+
+10.6.6: (tbd...)
+
+Change 11.1.1:
+
+   In the case of a scrollbar being placed on an edge of the element's
+   box, it should be inserted between the inner border edge and the
+   outer padding edge. Any space taken up by the scrollbars should be
+   subtracted from the computed width/height, thus preserving the
+   inner border edge.
+
+...to:
+
+   (tbd...)
+
+=Hixie= Work out the answer.
+http://annevankesteren.nl/test/css/temp/002.htm
 ------------------------------------------------------------------------
 Issue 151.
 Description:
@@ -3108,10 +3242,11 @@ Thanks,
 Jared
 
 Resolution:
-=WG= Discuss.
+=Bert= Resolve it.
 ------------------------------------------------------------------------
 Issue 152.
 URI: http://www.w3.org/mid/43D27CCC.9040709@mit.edu
+URI: http://www.w3.org/mid/21324932.1137881854316.JavaMail.ngmail@webmail-02.arcor-online.net
 Description:
 
 Based on previous discussion [1], I think it's clear the ::first-line
@@ -3125,7 +3260,23 @@ specification until such a time as it's better specified.
 [1] http://lists.w3.org/Archives/Public/www-style/2005Oct/0163.html
 
 (see equivalent selectors issue too)
+
+Further discussion including a testcase:
+   http://lists.w3.org/Archives/Public/www-style/2006Jan/0209.html
+
+Tantek's proposal:
+
+Put the ::first-line pseudo inside the inline elements.
+Paint the background separately, as for an anonymous box around the
+contents of the first line.
+
+Problems that remain with Tantek's proposal:
+
+Which background do you use, if ::first-line says "background: inherit"?
+What do you report for getComputedStyle(element, "::first-line") ?
+
 Resolution:
+
 =WG= Discuss.
 ------------------------------------------------------------------------
 Issue 153.
@@ -3138,26 +3289,148 @@ working group discussed this and concluded [2] that it would be best if
 this were specified by CSS.
 
 Resolution:
-=WG= Discuss.
+
+In section 14.2 add:
+
+   Intrinsic dimensions expressed as percentages must be resolved
+   relative to the dimensions of the rectangle that establishes the
+   coordinate system for the background-position property.
+
+   If the image has no intrinsic dimensions and has an intrinsic ratio
+   the dimensions must be assumed to be the largest dimensions at that
+   ratio such that neither dimension exceeds the dimensions of the
+   rectangle that establishes the coordinate system for the
+   background-position property.
+
+   If the image has no intrinsic ratio either, then the dimensions
+   must be assumed to be the rectangle that establishes the coordinate
+   system for the background-position property.
+
+=Bert= Edit.
 ------------------------------------------------------------------------
 Issue 154.
-URI: http://www.w3.org/mid/9882C98B3C3D9B45A9A5F9EDECE014D8155D13A1@win-msg-01.wingroup.windeploy.ntdev.microsoft.com
+URI:
+http://www.w3.org/mid/9882C98B3C3D9B45A9A5F9EDECE014D8155D13A1@win-msg-01.wingroup.windeploy.ntdev.microsoft.com
 Description:
 Resolution:
 Remove mso, add -ms, simplify table accordingly.
 =Bert= Edit.
 ------------------------------------------------------------------------
 Issue 155.
-URI: http://www.w3.org/mid/9882C98B3C3D9B45A9A5F9EDECE014D8155D14D3@win-msg-01.wingroup.windeploy.ntdev.microsoft.com
+URI:
+http://www.w3.org/mid/9882C98B3C3D9B45A9A5F9EDECE014D8155D14D3@win-msg-01.wingroup.windeploy.ntdev.microsoft.com
 Description:
 Resolution:
-=WG= Discuss at F2F.
-=David= Make proposal.
+=Markus= You raised the issue, you tell us how to resolve the issue.
 ------------------------------------------------------------------------
 Issue 156.
 URI: http://www.w3.org/mid/43F1094B.8000702@inkedblade.net
 URI: http://www.w3.org/mid/43F116DF.90409@inkedblade.net
 Description:
+text-decoration stuff (mostly minor stuff that should be ignored at
+this point, but there might be some potential issues)
+Resolution:
+=WG= Discuss.
+------------------------------------------------------------------------
+Issue 157.
+Description:
+Resolution:
+Mention in the Changes section that for changes not listed by Changes
+section, it's recommended that implementors read the disposition of
+comments.
+=Bert= Edit.
+------------------------------------------------------------------------
+Issue 158.
+Description:
+'no-wrap' should be 'nowrap' in 16.6.1:1.
+Resolution: Editorial.
+=Bert= Edit.
+------------------------------------------------------------------------
+Issue 159.
+Description:
+fantasai wants 6.4.1:2 to be s/style sheets/declarations/
+dbaron wants 6.4.1:4 to be s/rules/declarations/
+Resolution:
+=howcome= Edit.
+------------------------------------------------------------------------
+Issue 160.
+URI: http://www.w3.org/mid/9882C98B3C3D9B45A9A5F9EDECE014D815B23950@win-msg-01.wingroup.windeploy.ntdev.microsoft.com
+Description:
+selector wording
+Resolution:
+=WG= Discuss.
+------------------------------------------------------------------------
+Issue 161.
+URI:  http://www.w3.org/mid/9882C98B3C3D9B45A9A5F9EDECE014D8161032A5@win-msg-01.wingroup.windeploy.ntdev.microsoft.com
+Description:
+vertical-align and font-size
+Resolution:
+=WG= Discuss.
+------------------------------------------------------------------------
+Issue 162.
+Description:
+  From: Bob Jervis <bjervis@exchange.microsoft.com>
+  To: "howcome@opera.com" <howcome@opera.com>, "ian@hixie.ch" <ian@hixie.ch>
+  Cc: Markus Mielke <mmielke@windows.microsoft.com>
+
+  The CSS text is sketchy on the issue of line breaks.  Is a float a
+  line break opportunity?
+
+  This came up accidentally in composing a test page where I had
+  something like:
+
+                          Blah blah blah<span style="float: left">foo foo foo</span>, more blah blah blah
+
+  So there is no space between the 'blah' before the span and the ','
+  afterward.
+
+  Should a browser (formatting English just to avoid any
+  language-specific issues) ever allow a line break between the word and
+  the comma?  Visually, if you have some construct like:
+
+                          Xxx<span style="font: sans-serif">yyy</span>zzz
+
+  The xxx, yyy and zzz sub-sequences may appear very different, but I
+  could not find a browser that would line break that sequence.  Yet, I
+  did find that FireFox 1.5 (I think) does line break at a float.
+
+  What is the correct behavior?  There is language in the spec that says
+  floats should have no effect on vertical layout (relating to block
+  elements in the same flow), but I find no equivalent statement about
+  inline elements and text in the same flow.
+
+Resolution:
+=WG= Discuss.
+------------------------------------------------------------------------
+Issue 163.
+URI: http://www.w3.org/mid/440C62EC.3080403@mit.edu
+URI: http://www.w3.org/mid/440D5F48.4080307@peda.net
+URI: http://www.w3.org/mid/7.0.1.0.2.20060307100207.023631a8@nc.rr.com
+Description:
+wording in 10.3.2/10.6.2.
+bz's suggestions was:
+
+   If 'height' has a computed value of 'auto', 'width' also has a
+   computed value of 'auto', and the element has an intrinsic height,
+   the intrinsic height is the used value of 'height'.
+
+...and analogously for width.
+
+Resolution:
+=WG= Discuss.
+------------------------------------------------------------------------
+Issue 164.
+URI: http://www.w3.org/mid/440CFCDC.6030301@inkedblade.net
+Description:
+table backgrounds
+Resolution:
+=WG= Discuss.
+------------------------------------------------------------------------
+Issue 165.
+URI: http://www.w3.org/mid/E1FGhW7-00047U-G6@localhost.localdomain
+URI: http://www.w3.org/mid/440D7856.2060506@inkedblade.net
+Description:
+content: uri(404)
 Resolution:
 =WG= Discuss.
 ------------------------------------------------------------------------