[css2] More changes from the CSSWG F2F

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

Author: Hixie

css2/issues/issues-3

@@ -336,7 +336,7 @@ Further discussion at:
    http://www.w3.org/mid/200509141456.08425.bert@w3.org
 ...which may suggest better text.
 
-=Tantek= Edit. If you can find better ways of solving this, let us know.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 18.
 URI: http://lists.w3.org/Archives/Member/w3c-css-wg/2005JulSep/0034.html
@@ -481,7 +481,6 @@ Change "updated version" to "updated revision".
    changes: C
 
 Issue closed.
-=Hixie= Search for "version" when the spec is done.
 ------------------------------------------------------------------------
 Issue 25.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -563,8 +562,8 @@ a space.
 
 Be careful not to change the grammar token "stylesheet"!!
 
-Issue closed.
-=Hixie= Verify when the spec is done.
+=Bert= The word "Stylesheet" has slipped back into 11.1.1.
+=Bert= The word "CSS2.1" has slipped back into 4.3.5.
 ------------------------------------------------------------------------
 Issue 29.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -604,7 +603,7 @@ Resolution:
 Change "The list of tokens for CSS 2.1 is as follows." to "The list of
 tokens for CSS is as follows."
 
-=Tantek= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 31.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -631,7 +630,7 @@ can be parsed according to this grammar but not according to the
 grammar in Appendix G are among the parts that will be ignored
 according to the <a>rules for handling parsing errors</a>."
 
-=Tantek= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 32.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -761,7 +760,7 @@ Resolution:
 
 Add link in 4.1.2 to make this clearer.
 
-=Tantek= Edit.
+=Bert= The link is empty, it has no target (4.1.2).
 ------------------------------------------------------------------------
 Issue 37.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -779,7 +778,8 @@ Resolution:
 
 Add link.
 
-=Tantek= Edit.
+=Bert= Edit was made, but the comma at the end of the link is
+grammatically incorrect (4.1.2.1).
 ------------------------------------------------------------------------
 Issue 38.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -799,7 +799,7 @@ Resolution:
 
 Drop "2.1" and make it just "In CSS, identifiers..."
 
-=Tantek= Edit.
+=Bert= Edit. (4.1.2.1)
 ------------------------------------------------------------------------
 Issue 39.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -822,7 +822,7 @@ Answer is "yes", "property" and "property name" mean the same thing.
 Change "property" to "property name" in two places in 4.1.8: in first
 paragraph and in first paragraph after example.
 
-=Tantek= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 40.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -839,7 +839,7 @@ Resolution:
 
 Link "grammar" to the grammar, but leave the bit in parentheses.
 
-=Tantek= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 41.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -858,7 +858,7 @@ Resolution:
 
 Editorial, but move it to 4.1.
 
-=Tantek= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 42.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -878,7 +878,7 @@ Resolution:
 
 Do exactly what he asks for (in 4.1.5).
 
-=Tantek= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 43.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -895,7 +895,7 @@ Resolution:
 
 Do exactly what he asks for.
 
-=Tantek= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 44.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -919,7 +919,7 @@ Resolution:
 
 Change "characters" to "tokens" in that sentence but do nothing else. (4.1.6)
 
-=Tantek= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 45.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -957,7 +957,7 @@ Replace "{}-block" with "declaration block" throughout that section
 (used twice), and remove the "also called a" part that introduces the
 term in the first place. (4.1.7)
 
-=Tantek= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 47.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -1022,7 +1022,7 @@ Resolution:
 
 Don't split paragraph but change "character" to "token".
 
-=Tantek= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 49.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -1048,7 +1048,7 @@ Resolution:
 
 Change "and colors" to "colors, etc.".
 
-=Tantek= Edit.
+=Bert= Edit.
 ------------------------------------------------------------------------
 Issue 50.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -1211,7 +1211,7 @@ Resolution:
 Append "so that the resulting URI value is a URI token" to the end of
 the existing sentence.
 
-=Tantek= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 57.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -1244,7 +1244,7 @@ Resolution:
 
 Change CSS2 to CSS 2.1 here.
 
-=Tantek= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 59.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -1266,7 +1266,7 @@ Resolution:
 Append "with optional whitespace separating the tokens" at the end of
 the two sentences introducing counter syntax in 4.3.5.
 
-=Tantek= Edit. (Ask me if this makes no sense to you. -Hixie)
+Issue closed.
 ------------------------------------------------------------------------
 Issue 60.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -1284,7 +1284,7 @@ Resolution:
 
 Accepted.
 
-=Tantek= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 61.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -1302,7 +1302,7 @@ Resolution:
 
 Make both a link.
 
-=Tantek= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 62.
 URI: http://www.w3.org/mid/Pine.LNX.4.58.0507151120300.8454@localhost.localdomain
@@ -1664,8 +1664,7 @@ has not changed since the old CR.
 Resolution:
 Leave example, but David to write an extra example.
 
-=David= Propose additional example.
-=howcome= Edit.
+=howcome= Edit as per http://www.w3.org/mid/20060509145746.GA22598@ridley.dbaron.org
 ------------------------------------------------------------------------
 Issue 78.
 URI: http://www.w3.org/International/2005/05/css2-1-review.html#comt2-1
@@ -3293,9 +3292,6 @@ Resolution:
 
 Keep as is.
 
-=WG= if we keep this as is we'll have to mark our disposition of
-comments as having this as an open issue
-
 ISSUE UNRESOLVED -- INCLUDE IN DISPOSITION OF COMMENTS
 
 ------------------------------------------------------------------------
@@ -3531,7 +3527,6 @@ Resolution:
  identifiers (e.g. element names, classes, or IDs) may not." in
  section 4.1.3 bullet 2.
 
-=howcome= Confirm that you're ok with that.
 =Tantek= Edit.
 ------------------------------------------------------------------------
 Issue 168.
@@ -3674,14 +3669,117 @@ Issue 183.
 Description:
 How should error handling work in this test?:
 http://www.hixie.ch/tests/adhoc/css/parsing/uri/007.html
+
+Proposed resolution:
+
+Make the URI token match this in the two tokenisers:
+
+   url\({w}{string}{w}\)
+   |url\({w}{string}({escape}|[^)])*\)
+   |url\({w}([!#$%&*-~]|{nonascii}|{escape})*{w}\)
+   |url\(({escape}|[^)])*\)
+
+Add in section 4.3.4, after the sentence starting "Some characters",
+the following: "Specifically, when the URI is unquoted, only the
+following characters are valid: '!', '#', '$', '%', '&', and all
+characters in the range '*' to '~' in Unicode, as well as any
+character  above (but not including) U+007F. The '\' character must be
+handled as descripted in <a href="#escaped-characters">character
+escapes</a>. Other characters cause the URI token to be
+malformed. When the URI is quoted, the quoted part must be handled as
+a string token."
+
+Add in section 4.2 a new bullet "Malformed URI tokens": "UAs must
+handle URI tokens that do not follow the correct URI syntax described
+in the <a href="#uri">URLs and URIs</a> section by consuming all
+characters from the first character that does not match the syntax up
+to the first unescaped close parenthesis (")"). If the url() contents
+start with a quote mark, or whitespace followed by a quote mark, the
+UA must first find the end of the string before consuming characters
+in this way. (If the string is itself malformed, it must be handled as
+described below under the <a href="#@@@@">unexpected end of string</a>
+section.) The resulting token must cause the declaration to be ignored
+as a <a href="#@@@@">malformed declaration</a>. If the end of the
+stylesheet is reached before the matching parenthesis, the URI token
+construct must be closed as described below in the <a
+href="#@@@@">unexpected end of string</a> section."
+
 Resolution:
-=WG= Discuss.
+Require reparse. No change to spec.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 184.
 URI: http://lists.w3.org/Archives/Member/w3c-css-wg/2006AprJun/0101.html
+URI: http://www.w3.org/mid/20060511073448.GA4569@ridley.dbaron.org
 Description:
 Error in example in 12.4.1.
 Resolution:
 Editorial.
-=howcome= Edit.
-------------------------------------------------------------------------
+=howcome= Edit. (read both mails)
+------------------------------------------------------------------------
+Issue 185.
+URI: http://www.w3.org/mid/5.1.1.5.2.20060426114009.00c29b40@mailserver.nist.gov
+Description:
+Editorial issues from Tim.
+Resolution:
+Editorial
+=Bert= Edit.
+------------------------------------------------------------------------
+Issue 186.
+URI: http://www.w3.org/mid/20060511134503.GA6122@ridley.dbaron.org
+Description:
+Resolution:
+=Bert= Edit.
+------------------------------------------------------------------------
+Issue 187.
+URI: http://lists.w3.org/Archives/Public/www-style/2006Apr/0016.html
+Description:
+'overflow', when it's propagated, makes <html>/<body> have weird
+effects with floats.
+
+Resolution:
+Change the title of:
+
+   10.6.6 Block-level, non-replaced elements in normal flow when
+   'overflow' does not compute to 'visible'; 'inline-block', non-replaced
+   elements; and floating, non-replaced elements
+
+...to:
+
+   10.6.6 Complicated cases
+
+   <p>This section applies to:</p>
+
+   <ul>
+
+    <li> Block-level, non-replaced elements in normal flow when
+    'overflow' does not compute to 'visible' (except if the 'overflow'
+    property's value has been propagated to the viewport). </li>
+
+    <li> 'Inline-block', non-replaced elements. </li>
+
+    <li> Floating, non-replaced elements. </li>
+
+   </ul>
+
+Add to section 10.6.3:
+
+   <p>This section also applies to block-level non-replaced elements
+   in normal flow when 'overflow' does not compute to 'visible' but has
+   been propagated to the viewport.</p>
+
+Change section 9.4.1 where it says:
+
+   "Floats, absolutely positioned elements, inline-blocks,
+   table-cells, table-captions, and elements with 'overflow' other
+   than 'visible' establish new block formatting contexts."
+
+...to:
+
+   "Floats, absolutely positioned elements, inline-blocks,
+   table-cells, table-captions, and elements with 'overflow' other
+   than 'visible' (except when that value has been propagated to the
+   viewport) establish new block formatting contexts."
+
+=Bert= Edit.
+------------------------------------------------------------------------