[css2] Old issues and resolutions (from the F2F, I think)

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

Author: Hixie

css2/issues/issues-3

@@ -2255,6 +2255,9 @@ Issue closed.
 Issue 104.
 URI: http://www.w3.org/mid/430DB91A.2080905@cisra.canon.com.au
 URI: http://www.w3.org/mid/430DB941.9060204@cisra.canon.com.au
+Response: http://lists.w3.org/Archives/Public/www-style/2005Oct/0142.html
+URI: http://lists.w3.org/Archives/Public/www-style/2005Oct/0143.html
+Response: http://lists.w3.org/Archives/Public/www-style/2005Oct/0147.html
 Description:
 
 Section 4.2
@@ -2273,7 +2276,14 @@ grammars. Please allow other grammers (such as SVG) to add property values.
 
 -SVG
 
-=WG= Discuss.
+Property Resolution:
+
+Rejected. This statement only applies to text/css resources, which is
+the responsibility of the CSS working group; it is not a statment
+regarding the general W3C property namespace.
+
+=SteveZ= Talk to Chris to get better coordination going forward.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 105.
 URI: http://www.w3.org/mid/430DB9F0.7080409@cisra.canon.com.au
@@ -2290,12 +2300,13 @@ For example User Agents may use a process that provides mapping of the
 gamut to the device gamut in other ways, such as perceptual or
 photometric gamut mapping. This may involve compressing the full gamut
 of colours to fit inside the gamut of the output device, rather than
-simply clipping those outside the gamut so as to provide a better visual
-output. Please allow conformant UA's to perform higher quality gamut mapping.
+simply clipping those outside the gamut so as to provide a better
+visual output. Please allow conformant UA's to perform higher quality
+gamut mapping.
 
-Also please specify late clipping of colours as per CSS 2.0. Thus preserving colours
-until the final rendering step. This will also facilitate better colour
-quality.
+Also please specify late clipping of colours as per CSS 2.0. Thus
+preserving colours until the final rendering step. This will also
+facilitate better colour quality.
 
 -SVG
 
@@ -2306,7 +2317,14 @@ screen' style sheet are meant for an RGB monitor).
 <Bert> There is a property 'rendering-intent' in CSS3 Color, which may
 help with remapping.
 
-=WG= Discuss.
+Resolution:
+
+Insert "Users agents may perform higher quality mapping of colors from
+one gamut to another." just before the sentence that starts with "For
+a typical CRT monitor...".
+Then change "clipped" at the end of the section to "mapped".
+
+=Tantek= Edit.
 ------------------------------------------------------------------------
 Issue 106.
 URI: http://www.w3.org/mid/430DBA41.5080802@cisra.canon.com.au
@@ -2431,12 +2449,27 @@ Response: http://lists.w3.org/Archives/Public/www-style/2005Aug/0420.html
 URI: http://www.w3.org/mid/43156D79.1070402@disruptive-innovations.com
 URI: http://www.w3.org/mid/438E77CE.7010107@inkedblade.net
 URI: http://lists.w3.org/Archives/Public/www-style/2005Aug/0427.html
+Response: http://lists.w3.org/Archives/Public/www-style/2005Oct/0142.html (post-discussion)
+URI: http://lists.w3.org/Archives/Public/www-style/2005Oct/0143.html
+Response: http://lists.w3.org/Archives/Public/www-style/2005Oct/0147.html
+URI: http://lists.w3.org/Archives/Public/www-style/2005Oct/0151.html
+Response: http://lists.w3.org/Archives/Public/www-style/2005Oct/0156.html
 Description:
 Subject: Re: [CSS21] Unclear status of different versions
+Subject: Re: several messages
+Subject: Re: How to add properties to the CSS syntax
 From Chris on behalf of SVG and CDF.
 
-=WG= Discuss. Do we rescind CSS2? If not, what do we do about the fact
-that we have decided CSS2 is wrong on a huge number of issues?
+Resolution:
+
+In Abstract and Section 1.1, remove the sentence starting
+"Implementations may refer to CSS2...", and replace it with "Future
+specs should refer to CSS2.1 (unless they need features from CSS2
+which have been dropped in CSS2.1, and then they should only reference
+CSS2 for those features, or preferably reference such feature(s) in
+the respective CSS3 Module that includes those feature(s))."
+
+=Bert= Edit.
 ------------------------------------------------------------------------
 Issue 117.
 URI: http://www.w3.org/mid/265287321.20050825153955@w3.org
@@ -2496,7 +2529,19 @@ Perhaps the tutorials of 2.1, 2.2 are informative and the processing
 model 2.3 is normative? Its not clear whether 2.4 should be normative or
 informative.
 
-=WG= Discuss.
+Informative: 1.2, 1.3, 1.5, 2.1, 2.2, 2.4, A, C, D, F, I
+Normative: Everything else, including G.
+
+Resolution:
+Add to 3.1: "All sections of this specification, including appendices,
+are normative unless otherwise noted."
+In all places that are non-normative (as listed below) state "This
+section is non-normative."
+Those sections are: 1.2, 1.3, 1.5, 2.1, 2.2, 2.4, A, C, D, F, I
+Remove the statement in G that it is normative.
+Hyperlink 1.4.4 to 3.1, and 3.1 to 1.4.4. Update the reference to
+"CSS1" in 1.4.4 to just say "CSS".
+=Bert= Edit.
 ------------------------------------------------------------------------
 Issue 121.
 URI: http://www.w3.org/mid/1341455960.20050825154824@w3.org
@@ -2598,7 +2643,9 @@ must precede all other rules (except the @charset rule, if present)."
 (Incidentally, there's an error in media queries. It has an @import
 inside an @media block. Oops.)
 
-=WG= Discuss.
+Resolution:
+Approved. Make change described above.
+=howcome= Edit.
 ------------------------------------------------------------------------
 Issue 127.
 URI: http://www.w3.org/mid/43496FF1.6030306@inkedblade.net
@@ -2627,25 +2674,41 @@ rule in 17.5.1 in CSS2.)
 
 -Elika
 
-=WG= Discuss.
+Resolution:
+
+Add the following paragraph right after the list and before the
+paragraph following the list in section 1.7.5:
+
+   A "missing cell" is a cell in the row/column grid that is not
+   occupied by an element or pseudo-element. Missing cells are
+   rendered as if an anonymous table-cell box occupied their position
+   in the grid.
+
+=Bert= Edit.
 ------------------------------------------------------------------------
 Issue 128.
 URI: http://www.w3.org/mid/4315C787.6030203@comhem.se
 Description:
 shrink-to-fit issue.
-=WG= Discuss.
+Resolution:
+He is wrong.
+=David= Reply.
 ------------------------------------------------------------------------
 Issue 129.
 URI: http://www.w3.org/mid/43187BCC.3050109@easyconnect.fr
 Description:
 error handling of selectors
-=WG= Discuss.
+Resolution:
+Add reference from 4.2 to 4.1.7.
+=Tantek= Edit.
 ------------------------------------------------------------------------
 Issue 130.
 URI: http://lists.w3.org/Archives/Member/w3c-css-wg/2005JulSep/0196.html
 Description:
 Some things in 4.1.1 still say [a-zA-Z].
-=WG= Discuss.
+Resolution:
+Assumed editorial.
+=Tantek=
 ------------------------------------------------------------------------
 Issue 131.
 URI: http://www.w3.org/mid/e474a6b0ffb3c208411115775fe0b074@asahi-net.or.jp
@@ -2659,21 +2722,30 @@ Issue 132.
 URI: http://www.w3.org/mid/9882C98B3C3D9B45A9A5F9EDECE014D812686BF9@win-msg-01.wingroup.windeploy.ntdev.microsoft.com
 Description:
 Clarify rule about pseudo-elements not being anywhere but the end of a rule.
-=WG= Discuss.
+Resolution:
+Retracted by reporter.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 133.
 URI: http://www.w3.org/mid/20050919225223.GA9168@ridley.dbaron.org
 Description:
 List numbering in 2.1.
-=WG= Discuss.
+Resolution:
+Remain silent. Address in test suite.
+=Hixie= Put
+http://dbaron.org/css/test/2005/list-numbering-across-types in the
+test suite along with many other tests on this.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 134.
 URI: http://www.w3.org/mid/n2m-g.5tqkj11nfnmho9ijthjsj51um88q0r9kvm@news.spartanicus.utvinternet.ie
 URI: http://www.w3.org/mid/n2m-g.shskj1hnqnk0u1q1096r4aurdeaekhfl0i@news.spartanicus.utvinternet.ie
 Description:
 http://www.w3.org/TR/CSS21/changes.html#q4 currently doesn't mention
 the new value "none" for the "content" property, and other comments.
-=WG= Discuss.
+Resolution:
+Assumed editorial.
+=Bert= Edit.
 ------------------------------------------------------------------------
 Issue 135.
 URI: http://www.w3.org/mid/20050929151808.12625@mail.visualclick.de
@@ -2685,5 +2757,34 @@ I seem to have lost the place where it is defined how to establish the
 size of the page box (<http://www.w3.org/TR/CSS21/page.html>). I think
 this used to be done with the 'size' property in CSS2, but this is no
 longer in CSS21.
-=WG= Discuss.
+Resolution:
+=howcome= Reply.
+------------------------------------------------------------------------
+Issue 136.
+Description:
+Many of the normative refs should be informative.
+PNG, HTML4, CSS1, CSS2, XML10 etc might not want to be normative. But
+we should check.
+[CHARSETS] maybe should be normative?
+Resolution:
+=David= Check all the references for whether they should be norm/non-norm.
+------------------------------------------------------------------------
+Issue 137.
+Description:
+Resolution:
+Change or remove the copyright in chapter 1. (1.6)
+=Bert= Edit.
+------------------------------------------------------------------------
+Issue 138.
+Description:
+PDF is broken (appendices out of order).
+Resolution:
+=Bert= Fix.
+------------------------------------------------------------------------
+Issue 139.
+Description:
+[PNG]'s URI is old.
+[URI]'s reference's description is missing. (RFC problem)
+Resolution:
+=Bert= Edit.
 ------------------------------------------------------------------------