The vast majority of editorial comments are not acknowledged here but have been incorporated.
Last modification: Michel Suignard, Wed, March 12 2003
| # | source | origin | date | comment | answer |
|---|---|---|---|---|---|
| 1 | Bert Bos (Bert.Bos@sophia.inria.fr) |
w3c-css-wg | 17-Feb |
http://lists.w3.org/Archives/Member/w3c-css-wg/2003JanMar/0187.html In section 4.1, 'text-align' should not say that 'start, end' are preferred over 'left, right' |
Document updated: the description value does not express a 'preference' anymore. The new sentence says:" Unlike the 'start' and 'end' values, the 'left' and 'right' are not related to the current inline-progression." |
| 2 | In section 4.1, 'text-align' is missing 'top' and 'bottom' | It doesn't seem useful to add even more 'physical' values to property that have an inherent dependency on the text flow. Authors dealing with vertical flow have a much better grasp of flow orientation by necessity. | |||
| 3 | In section 4.3, 'text-align-last' is missing 'top', 'bottom', 'left' and 'right' | Document updated: added 'left' and 'right' to 'text-align-last' for consistency with 'text-align'. (see comment #2 for the rationale for not adding the other values) | |||
| 4 | Gustav Svensson (gurra16@spray.se) | www-style | 27-Feb |
hhttp://lists.w3.org/Archives/Public/www-style/2003Feb/0251.html Section 9. The blink frequency should be configurable. |
There is a large majority view in the CSS group to keep blink as it is. Note that 'text-blink' is now available as a separate property. |
| 5 | Ian Hickson (ian@hixie.ch) |
w3c-css-wg | 28-Feb |
http://lists.w3.org/Archives/Member/w3c-css-wg/2003JanMar/0255.html Section 9.1, clarify text decoration on 'empty' element |
Document updated as suggested (with minor editorial changes) |
| 6 | Ian Hickson (ian@hixie.ch) | w3c-css-wg | 28-Feb |
http://lists.w3.org/Archives/Member/w3c-css-wg/2003JanMar/0251.html Inaccurate computed values for 'text-align', 'text-first-indent', 'text-indent', 'letter-spacing', 'word-spacing, 'kerning-pair-threshold', 'text-underline-width', 'text-shadow' and 'line-grid-progression' |
Document updated as suggested (except for 'text-indent' and 'text-first-indent' which are subject to another comment) |
| 7 | The 'inherited' line should not apply to shorthand properties | It does not really matter because all constituent properties in all these cases have the same inheritance behavior. In principle, it should be left to each constituent property definition. This is a cross module matter, but the document can stay as it is for now. | |||
| 8 | Text-indent section overly complex | Document updated. The property 'text-indent' is reverted to what it used to be with the added 'hanging' keyword. However the indentation stays related to the starting edge, not the alignment edge. | |||
| 9 | Interaction between 'letter-spacing' and 'word-spacing' not very well defined. | Document updated: Added: 1) a white space character is a grapheme cluster. 2) letter-spacing should not apply to zero-width characters but all applies to all non collapsed white space characters.3) word-spacing should not be applied to zero-width word boundaries (or implied boundaries) 4) word-spacing only applies once to a sequence of non collapsed white spaces 5) letter-spacing and word-spacing are cumulative | |||
| 10 | Remove bulleted list in the definition of 'collapse' in 'all-space-treatment' | Document updated as suggested | |||
| 11 | fantasai@escape.com | www-style | 02-Mar |
http://lists.w3.org/Archives/Public/www-style/2003Mar/0010.html The error about 'direction' value being switched for 'writing-mode: bt-lr' not corrected |
Document updated: changed the instance of 'rtl' to 'ltr' in the value description. |
| 12 | Affect of Glyph Orientation on Character Ordering | Document updated: made clear that the reordering only applies to specific value of the Glyph Orientation properties. Using range would be a nice extension but can wait a future version. | |||
| 13 | Fix the Rotating Image Examples in section 3.2 | Document updated as suggested | |||
| 14 | Line-breaking in Perpendicular Inline Blocks | Document updated: Removed the 2 last sentences of the example section (Line breaking is ...property setting) and added the following text "In such cases, the content height of the element within the line box is determined by its maximum inline progression dimension (advance width). The resulting line height is however determined by other properties such as the 'text-height' and the 'line-stacking-strategy' [link to the CSS3 Line module]." to the description concerning inline-level elements. | |||
| 15 | Direction: Interpretation of 'ltr' and 'rtl', replace 'line direction' by 'block progression'. | Document updated as suggested | |||
| 16 | Interaction of Writing-Mode and Direction Don't cascade |
Document updated: made writing-mode a shorthand and added a new property to handle block progression: 'block-progression'. This is a significant change. | |||
| 17 | fantasai@escape.com | www-style | 02-Mar |
http://lists.w3.org/Archives/Public/www-style/2003Mar/0012.html Editorial changes |
Document updated, with the caveat that some changes were made N/A following disposition of comment #16. |
| 18 | Susan Lesch (lesch@w3.org) | www-style | 05-Mar |
http://lists.w3.org/Archives/Public/www-style/2003Mar/0032.html Change title to CSS3 Module: Text |
Document updated, changed to "CSS3 module: Text" to be consistent with other module titles |
| 19 | Replace 'linefeed' by 'line feed' in text and add a hyphen (like in 'line-feed) for property names [and values?] | Document updated: replace 'linefeed' by 'line feed' in text, but kept property names and value unchanged for consistency with XL | |||
| 20 | Other editorial requests, typos | Document updated as suggested | |||
| 21 | fantasai@escape.com | www-style | 05-Mar |
http://lists.w3.org/Archives/Public/www-style/2003Mar/0033.html Conformance Requirements for glyph-orientation-vertical: remove first level and redundant conformance text |
Document updated as suggested |
| 22 | Interpretation of Degree Values in glyph-orientation-vertical, change to 'relative to block-progression' (instead of inline-progression) and value descriptions | Document updated as suggested, with some minor edits (added that the glyph orientation is also related to the block box bottom) | |||
| 23 | Affect of glyph orientation on bidi groupings, clarify rounding behavior and the word reset. | Document updated, a new sentence added in the glyph orientation intro: "When text behavior is related to a specific glyph orientation value, it is implied that it also applies to all values that would be equivalent if rounded to the nearest multiple of 90 degrees." and the sentence about resetting the bidi algorithm replaced by: "If applied to an inline element, the boundaries of the element acquire the directionality of the nearest block ancestor. " | |||
| 24 |
Brackets in vertical text, what happens to non-ideographic punctuation? If its orientation is 0deg? |
In short: nothing. This is the whole point of using the 'auto' value which is in effect letting smart fonts drive the glyph orientation values in vertical flow. The UA should not have to redo something which is naturally achieved by font design. | |||
| 25 |
References to CSS3 Block &Line, simplify reference
|
Document updated as suggested | |||
| 26 |
Embedded Objects, say that images are treated as object replacement characters and delete the related note. |
Document updated as suggested | |||
| 27 | fantasai@escape.com | www-style | 05-Mar |
http://lists.w3.org/Archives/Public/www-style/2003Mar/0035.html Text-script: auto heuristic |
Document updated, added text that says that heuristic is user agent dependent and hints at more sophisticated mechanisms. |
| 28 | fantasai@escape.com | www-style | 06-Mar |
http://lists.w3.org/Archives/Public/www-style/2003Mar/0045.html text-align, 'left' and 'right' value, the alignment should not be UA dependent. |
Document updated as suggested |
| 29 | No justification option allowing kashida, word-spacing for Latin, and letter-spacing for CJK, shouldn't kashida mode allow letter-spacing for Kashida | Typically each justification option is biased toward one script (in the case of Kashida, it is Arabic). Allow letter-spacing for CJK in CJK would make the implementation of the 'text-kashida-space' more complicated. Mixing Arabic with CJK is also extremely rare. | |||
| 30 | Last Line alignment, make it dependent on 'text-align' set to 'justify'. | Document updated as suggested. | |||
| 31 | Will the restricted definition of min/max-font-size in CSS3 preclude generalizing its use in later specs? | I don't see why that would be an issue | |||
| 32 |
'text-justify-trim', fix typo in value description (punct-and-kana), replace by [puntuation || kana] |
Document updated, typo corrected. However values stay are they are. There is value in having a simple enumeration instead of a list for a value type, especially because in this case, you wouldn't compress 'kana' if you had not already compressed 'punctuation'. | |||
| 33 | CSS WG | Mar | Face to face meeting during the Boston W3C technical plenary
March 2003 Removed new values added in text-underline-mode, text-line-through-mode and text-overline-mode to skip over character ink |
Document updated, however the term 'skip-white-space' stays (instead of the original 'words') | |
| 34 | fantasai@escape.com | www-style | 21-Mar |
http://lists.w3.org/Archives/Public/www-style/2003Mar/0154.html Bidi in vertical context |
Document updated, many ideas from the feedback have been incorporated, new values added to glyph-orientation-vertical and glyph-orientation-horizontal which were completely rewritten. |