[css2] Make issues list up to date.

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

Author: Hixie

css2/issues/issues-3

@@ -421,10 +421,7 @@ Editorial.
 
 For Unicode, resolution is to refer to latest (dynamic).
 
-=Bert= Edit.
-
-(Bert - is this done? What edit did you make? I couldn't work out what
-to verify. -Hixie)
+Issue closed.
 ------------------------------------------------------------------------
 Issue 23.
 URI: http://www.w3.org/mid/AAAB784B-9C78-4C1C-9403-092E7BA57916@w3.org
@@ -712,6 +709,7 @@ Issue closed.
 ------------------------------------------------------------------------
 Issue 35.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
+Response: http://lists.w3.org/Archives/Public/www-style/2005Oct/0141.html
 Description:
 
 > Suggestion of sectioning:
@@ -734,7 +732,7 @@ We will consider this for CSS3, but it doesn't seem appropriate for
 CSS2.1 right now (not a change of functionality, so too late at this
 time to change 2.1).
 
-=Bert= Reply.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 36.
 URI: http://www.w3.org/mid/20050713212905.652@mail.visualclick.de
@@ -1316,8 +1314,10 @@ Resolution:
 Keep definiton of 'empty-cells' as is (i.e., doesn't apply to
 collapsed borders).
 
-=Elika= to propose a new example for 17.5.1. (Waiting for issue 127.)
-=Bert= Edit once a new example is ready.
+Elika came up with replacement text and images:
+   http://www.w3.org/mid/438820C2.6060800@inkedblade.net
+
+=Bert= Edit.
 ------------------------------------------------------------------------
 Issue 63.
 URI: http://www.w3.org/mid/Pine.LNX.4.58.0507151327520.10214@localhost.localdomain
@@ -1343,7 +1343,7 @@ Change quotes sentence to:
 content, then the row has zero height and there is vertical
 border-spacing on only one side of the row."
 
-=Bert= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 64.
 URI: http://www.w3.org/mid/i51ekacjbi2.wl@w3.mag.keio.ac.jp
@@ -1405,7 +1405,7 @@ s/If a subsequent row has more columns than the first,/If a subsequent
 row has more columns than the greater of the number determined by the
 table-column elements and the number determined by the first row,"
 
-=Bert= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 68.
 URI: http://lists.w3.org/Archives/Member/w3c-css-wg/2005JulSep/0064.html
@@ -1514,7 +1514,7 @@ Resolution:
 add right before "10.6.1":  Note:  these rules apply to
 the root element just as to any other element.
 
-=Bert= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 72.
 URI: http://www.w3.org/mid/op.svanzwqtsmjzpq@r600
@@ -1527,7 +1527,7 @@ Resolution:
 
 Assumed editorial. (See e-mail, it has a list.)
 
-=Bert= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 73.
 Description:
@@ -1703,15 +1703,15 @@ to be ignored.  Change
 to say that C must not be empty (and perhaps that it should be an
 identifier).
 
-=Bert= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 81.
 URI: http://www.w3.org/International/2005/05/css2-1-review.html#comt2-4
 Description:
 i18n review comment 4: Phrasing of RFC3066 reference.
 Resolution:
 Assumed editorial.
-=Bert= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 82.
 URI: http://www.w3.org/International/2005/05/css2-1-review.html#comt2-5
@@ -1779,10 +1779,11 @@ i18n review comment 6: Update Unicode and other i18n references.
 See also issues 22 (Unicode) and 72 (General).
 Resolution:
 Assumed editorial.
-=Bert= Edit.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 84.
 URI: http://www.w3.org/International/2005/05/css2-1-review.html#comt2-7
+Response: http://lists.w3.org/Archives/Member/w3c-css-wg/2005OctDec/0022
 Description:
 i18n review comment 7: @font-face
 See also issue 136b in issues-1.
@@ -1794,11 +1795,13 @@ require going back to Last Call and we would probably have to use
 SVG implementations to exit CR if at all possible.
 -Bjoern
 
-=Bert= Email i18n asking exactly which features they want (and whether
-they can write good testcases for them).
+Awaiting further reply.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 85.
 URI: http://www.w3.org/International/2005/05/css2-1-review.html#comt2-8
+Response: http://lists.w3.org/Archives/Member/member-i18n-core/2005Oct/0017.html
+URI: http://lists.w3.org/Archives/Member/w3c-css-wg/2005OctDec/0107
 Description:
 i18n review comment 8: Request for UTF-16 to be mandatory
 (Since XML implementors often try to get out of implementing UTF-16,
@@ -1816,10 +1819,7 @@ the requirement to support UTF-16.
 Resolution:
 No change.
 
-Elika drafted response:
-   http://lists.w3.org/Archives/Member/w3c-css-wg/2005OctDec/0029.html
-
-=Bert= Send e-mail.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 86.
 URI: http://www.w3.org/International/2005/05/css2-1-review.html#comt2-9
@@ -1840,7 +1840,7 @@ seems the .htaccess did not make it...
 
 Resolution:
 Assumed editorial.
-=Bert= Investigate.
+Issue closed.
 ------------------------------------------------------------------------
 Issue 88.
 URI: https://bugzilla.mozilla.org/show_bug.cgi?id=295309
@@ -2137,9 +2137,58 @@ it.
 
 -Bert
 
-Resolution:
+Bert had an action to come up with some text and came up with these
+two alternatives:
+
+   http://lists.w3.org/Archives/Member/w3c-css-wg/2005OctDec/0063
+   http://www.w3.org/mid/200511071925.10288.bert@w3.org
+
+The latter is:
+
+   The 'ex' unit is defined by the font's 'x-height'. 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".
+  
+   UAs must follow the following algorithm to establish the 'ex' for a
+   given element:
+  
+      1. Using the algorithm for font selection (section 15.2), find
+         the font that would be used for rendering an "x".
+  
+      2. Set the 'ex' to the x-height defined by that font; or draw
+         the "x" (in an off-screen buffer) and measure its height.
+  
+      3. If it is impossible to find an x-height or measure an "x"
+         glyph, use 0.5em.
+  
+   UAs should take care that the 'ex' they compute in step 2 is
+   reasonable.  In many fonts, the height of an "x" is not equal to
+   the x-height (e.g., because the x has a decorative flourish). On
+   the other hand, experience shows that many fonts don't define an
+   x-height or define it incorrectly.
+
+Ian responded to the first of these with a suggestion to change the
+following paragraph now in the spec:
+
+   The 'ex' unit is defined by the font's 'x-height'. 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".
 
-=Bert= Come up with some text (discussed at SF plenary, Monday afternoon).
+...to read:
+
+   The 'ex' unit is defined by the element's first available font's
+   'x-height' metric. The element's first available font is the one that
+   is found using <a>the font matching algorithm</a>, but without limiting
+   the search to fonts that contain particular characters.
+
+   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". User agent should use font metrics or direct
+   glyph measurement if possible, but may fall back on a default of 0.5em
+   if the first available font does not contain suitable information.
+
+=WG= Discuss.
 ------------------------------------------------------------------------
 Issue 96.
 URI: http://www.w3.org/mid/430B4766.8070004@tu-clausthal.de
@@ -2282,8 +2331,10 @@ 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.
+SZ sent http://www.w3.org/mid/6.2.1.2.2.20051201104905.0f7e1db0@namailhost.corp.adobe.com
+WG discussed but disagreed with the conclusion.
+
+=WG= Discuss further.
 ------------------------------------------------------------------------
 Issue 105.
 URI: http://www.w3.org/mid/430DB9F0.7080409@cisra.canon.com.au
@@ -2788,3 +2839,41 @@ Description:
 Resolution:
 =Bert= Edit.
 ------------------------------------------------------------------------
+Issue 140.
+URI: http://www.w3.org/mid/7AEA6A97-B533-4707-87A3-A4BE386A4CFF@apple.com
+URI: http://www.w3.org/mid/37891D60-D98A-47AF-AD51-2323D2AC6454@apple.com
+URI: http://www.w3.org/mid/F9AA656B-D48C-4043-A65F-BB7461BC74A9@apple.com
+Description:
+pre-wrap issue.
+=WG= Discuss.
+------------------------------------------------------------------------
+Issue 141.
+URI: http://www.w3.org/mid/4383ABE2.5010905@mit.edu
+Description:
+I think 6.4.1 needs to be clearer about the sort at each step being
+only within groups of rules that sorted equivalent to each other at
+the previous step...  That's not obvious from just looking at the
+text, as things stand. -Boris
+
+=WG= Discuss.
+------------------------------------------------------------------------
+Issue 142.
+URI: http://www.w3.org/mid/20051123002259.GA27719@ridley.dbaron.org
+
+> "User agent: Conforming user agents must apply a default style sheet
+> (or behave as if they did) prior to all other style sheets for a
+> document....."
+
+We should just remove the words "prior to all other style sheets for a
+document", since they're redundant and potentially confusing if
+interpreted too literally. -dbaron
+
+=WG= Discuss.
+------------------------------------------------------------------------
+Issue 143.
+Description:
+Margin and padding properties should apply to table-caption (they
+currently say they don't despite the table section defining how
+margins work for table-caption boxes).
+=WG= Discuss.
+------------------------------------------------------------------------