CSS2.1
The CSS2.1 specification is a revision of of CSS2 that corrects many errors and omissions in the CSS2 Recommendation. It has also dropped unimplemented features and introduced a handful of minor new ones.
TODO: Audit issues list and make sure each issue has tests in the test suite. Then institute policy that issues cannot be marked as closed until there is a test checked in for that issue.
CSS 2.1 bugs/issues are no longer tracked on this wiki page. New issues on CSS 2.1 should go in Bugzilla. (See existing open bugs, or file a new bug but please discuss on the (archived) public mailing list www-style@w3.org (see instructions) first). From there, they find their way to the errata document.
Mailing list sweeps:
TODO: perform mailing list sweep for Jan to April 2011; perform sweep for 2010 specifically looking for items marked for consideration in errata; comprehensively review this wiki page to ensure that errata items are captured and moved to Bugzilla (antonp).
Current Issues
Issue 142
- URL
- http://lists.w3.org/Archives/Public/www-style/2009Sep/0126.html #4
- Summary
- clarify terms like “ancestor box”, whether referring to formatting structure or document tree. Spec contains only 3 instances of ancestor box. They are all in section 10.1.
- Resolution
- Agreed this is ambiguous.
- Proposal
- first version, second version, with support for run-in
- Follow-up 1
- There is probably an error in the resolution of issue 120. If so, the proposal needs changing.
- Follow-up 2
- Boris Zbarsky asks that the containing block of an element inside a table, in the absence of a table element, be created from the height of the row and the width of the column, even if one or both of those are implied rather than actual elements. If we accept that change, the proposal needs changing.
- Resolution
- Push to errata.
- Status
- Open. =errata=
Issue 153
- URL
- http://lists.w3.org/Archives/Public/public-css-testsuite/2010Jan/0030.html
- Summary
- Clarify which box of a replaced element is vertical-aligned
- Testcase
- http://www.w3.org/Style/CSS/Test/CSS2.1/20100127/html4/c44-ln-box-002.htm
- Testcase
- data:text/html;charset=utf-8,%3C!DOCTYPE%20html%3E%0D%0A%3Cp%20style%3D%22border%3A%201px%20solid%20gray%3B%22%3E%3Cspan%20style%3D%22background%3A%20silver%3B%22%3EXx-%20%3Cimg%20src%3D%22http%3A%2F%2Ftest.csswg.org%2Fsource%2Fapproved%2Fsupport%2Fsquare-purple.png%22%20style%3D%22vertical-align%3A%20middle%3B%20margin-top%3A%20100px%3B%20border%3A%20solid%2010px%20aqua%3B%20border-bottom-width%3A%2040px%3B%22%3E%20-xX_
- Proposal
- “In the following definitions, for replaced, inline-block, and inline-table elements, the box used for alignment is the margin box. For inline non-replaced elements, the box used for alignment is undefined.”
- Second proposal
- http://lists.w3.org/Archives/Public/www-style/2010Jun/0570.html
- Resolution
- Second proposal accepted.
- Follow-up 1
- The term “the box whose height is 'line-height'” isn't actually defined anywhere and indeed can't be. (The intended boxes are typically of that height, but it depends on whether they contain glyphs in fallback fonts.) We need to define the box we need somewhere, or characterize it better. See thread. See also sylvain's comment in the March f2f minutes
- Status
- Closed.
- Testcases
- vertical-align-boxes-001
Issue 159
Issue 179
Issue 181
Issue 192
Issue 197
Issue 198
- Summary
- Clarify interaction of run-ins and “elements earlier in the source document”.
- URI
- http://lists.w3.org/Archives/Public/www-style/2010Jan/0376.html
- Proposal
- Say that for all layout purposes, the run-in is considered a direct child of the block to which it belongs.
- Resolution
- Move run-in to CSS3 Box.
- Status
- Closed.
Issue 199
Issue 203
Issue 204
Issue 205
Issue 206
Issue 207
Issue 208
Issue 209
Issue 210
Issue 211
Issue 212
- Summary
- Clarify that table wrapper boxes are containing blocks, even though table boxes are not in 9.2.1
- Resolution
- Clarified by edits for other issues.
- Status
- Closed.
Issue 213
Issue 214
Issue 215
- Summary
- Make it undefined what containing block is formed by a relpos inline that splits across multiple lines
- URI
- containing-block-032
- Resolution
- Make undefined.
- Status
- Closed.
Issue 216
- Summary
- Drop vertical-align from list of properties supported on ::first-line
- URI
- first-line-pseudo-016
- Resolution
- Drop.
- Status
- Closed.
Issue 218
Issue 219
Issue 220
Issue 221
- Summary
- Remove gamma-correction section
- URI
- Resolution
- Remove gamma-correction section
- Status
- Closed.
Issue 222
Issue 223
Issue 224
Issue 225
Issue 226
Issue 227
Issue 228
Issue 229
Issue 230
Issue 231
Issue 232
Issue 233
Issue 234
Issue 235
Issue 236
Issue 237
Issue 238
Issue 239
Issue 240
Issue 241
Issue 242
- Summary
- Exact behavior of inline split around block not defined.
- URL
- http://lists.w3.org/Archives/Public/www-style/2010Nov/0047.html (z-index issues folded into issue 244)
- Proposal
- “are broken around the block-level box (and any block-level siblings that are consecutive or separated only by collapsible whitespace and/or out-of-flow elements), splitting the inline box into two boxes (even if either side is empty), one on each side of the block-level box.”
- Resolution
- Proposal accepted.
- Status
- Closed.
Issue 243
Issue 244
Issue 245
Issue 246
Issue 247
Issue 248
Issue 249
Issue 250
Issue 251
Issue 252
Issue 253
Issue 254
Issue 255
Issue 256
Issue 257
Issue 258
Issue 259
Issue 260
Issue 261
Issue 262
Issue 263
Issue 264
Issue 265
Issue 266
- Summary
- Issue 120 follow-up
- URL
- http://lists.w3.org/Archives/Public/www-style/2011Jan/0079.html
- Proposal :
Accept proposals 1 & 2 with “block container element” instead of “block container”
accept 3
accept 4
accept 5 with s/which/that/
accept 7 (but beware second set of edits applies to second quoted sentence, not first)
- Resolution
- Accept issue 6 edits, push rest to errata.
- Status
- Closed. =errata=
Issue 267
Issue 268
Issue 269
Issue 270
Issue 271
Issue 272
Issue 273
Issue 274
Issue 275
Issue 276
Issue 277
Issue 278
Issue 279
Issue 280
Issue 281
Issue 282
- Summary
- No passes for background-intrinsic-004 and background-intrinsic-005
- Resolution
- The background position of background images with an intrinsic ratio and no intrinsic size is undefined in CSS2.1, see CSS3 Backgrounds and Borders.
- Status
- Closed.
Issue 283
Issue 284
- Summary
- CSS2.1 exit criteria differ from CSS3
- Resolution
- Update CSS 2.1 exit criteria to the current (CSS3 standard) exit criteria, minus the 30-day implementation requirement.
- Status
- Duplicate of issue 272.
Issue 285
Issue 286
Issue 287
Issue 288
8 September 2009 CR Issues
Issue 53
Issue 56
Issue 60
Issue 69
- URL
- http://lists.w3.org/Archives/Public/www-style/2008Aug/0126.html
- Summary
- fixed background images not defined for paged media
- Proposal
- Add “In paged media where there is no viewport, a ‘fixed’ background is fixed with respect to the page box and is therefore replicated on every page.” (Copied from css3-background)
- Resolution
- Proposal accepted.
- Status
- Closed.
- Testcases
- background-attachment-010
Issue 86
Issue 109
Issue 110
Issue 111
Issue 118
Issue 120
Issue 121
Issue 122
Issue 128
Issue 129
Issue 137
Issue 138
Issue 139
Issue 140
Issue 143
Issue 144
Issue 145
Issue 146
Issue 147
Issue 148
Issue 149
Issue 150
Issue 151
Issue 152
Issue 155
Issue 160
Issue 161
Issue 167
Issue 168
Issue 170
Issue 171
Issue 172
Issue 173
Issue 175
Issue 180
Issue 182
Issue 183
- Summary
- Error handling of malformed media types underdefined.
- URI
- http://lists.w3.org/Archives/Public/www-style/2010Aug/0025.html
- Resolution
- Change “@media and @import rules with unknown media types are treated as if the unknown media types are not present.” to “@media and @import rules with unknown media types (that are nonetheless valid identifiers) are treated as if the unknown media types are not present. If an @media rule contains a malformed media type (not an identifier) then the statement is invalid.” and add “Note: Media Queries supercedes this error handling.”
- Status
- Closed.
Issue 185
Issue 186
Issue 187
Issue 190
Issue 191
Issue 193
- Summary
- Add note to 6.2 clarifying that inheritance operates on the element tree and does not get intercepted by anonymous boxes.
- URI
- None
- Resolution
- Assumed editorial. Needs tests, though.
- Status
- Closed. =fantasai= tests
Issue 194
Issue 195
Issue 196
- Summary
- Grammar and prose disagree on whether identifiers can include NBSP
- URI
- http://lists.w3.org/Archives/Public/www-style/2010Feb/0156.html
- Notes
- Opera, and Konqueror allow nbsp in identifiers; Firefox does not
- Testcase
- data:text/xml;base64,PGh0bWwgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGh0bWwiPg0KPGhlYWQ%2BDQo8c3R5bGU%2BDQogICYjeDcwOyB7IGNvbG9yOiBncmVlbjsgfQ0KICAudGVzdCB7IGNvbG9yOiByZWQ7IH0NCiAgLnRlc3QmI3hBMDtzZW50ZW5jZSB7IHRleHQtZGVjb3JhdGlvbjogdW5kZXJsaW5lOyB9DQo8L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHk%2BDQo8cCBjbGFzcz0idGVzdCYjeEEwO3NlbnRlbmNlIj5UaGlzIHNlbnRlbmNlIG11c3QgYmUgZ3JlZW4uIElzIGl0IHVuZGVybGluZWQ%2FPC9wPg0KPC9ib2R5Pg0KPC9odG1sPg%3D%3D
- Resolution
- Identifiers can contain nbsp. Update spec to include nbsp and exclude control characters adjacent to it.
- Status
- Closed.
Issue 201
Issue 217
8 September 2009 CR Issues
23 April 2009 CR Issues
Issue 25
Issue 26
Issue 61
Issue 71
- URL
- Summary
- @rules in unexpected contexts should parse as @rules.
- Old Resolution
- @rules inside declaration blocks are ignored if between declarations (i.e. at the beginning of a declaration before the property), invalid if within declarations.
- Proposal
- http://lists.w3.org/Archives/Public/www-style/2010Apr/0447.html changes a, b (optional), c (optional), and d.
- Resolution
- Bert's proposal accepted
- Status
- Closed.
- Testcases
- at-page-rule-001 and declarations-009
Issue 72
Issue 73
- URL
- http://lists.w3.org/Archives/Public/www-style/2008Sep/0216.html
- Summary
- URL grammar and comments
- Proposal
- No change. Comments are not allowed inside url(). Add a note to clarify.
- Resolution
- Proposal accepted.
- Proposed Note
- In Section 4.3.4 add the following paragraph (best place is probably after “Depending on the type of URI…”: “Since URIs may contain characters that would otherwise be used as delimiters in CSS, the entire URI value must be treated as a single unit by the tokenizer and normal tokenization behavior does not apply within a URI value. Therefore comments are not allowed within a URI value.”
- Status
- Closed.
- Testcases
- uri-016
Issue 75
Issue 84
Issue 89
Issue 101
Issue 107
Issue 114
- URL
- http://lists.w3.org/Archives/Public/www-style/2009Apr/0325.html
- Summary
- font-family syntax ambiguous
- Proposal 1
- http://lists.w3.org/Archives/Public/www-style/2010Mar/0369.html
- Proposal 2
- http://lists.w3.org/Archives/Public/www-style/2010Mar/0395.html
- Testcases
- * http://test.csswg.org/source/contributors/microsoft/submitted/Chapter_15/font-family-invalid-characters-001.xht
IE8: Fails: # + /
FF3.6: Pass
O10.51: Fails: @ # * /
S4.0.5: Pass
-
IE8: Fail
FF3.6: Fail
O10.51: Fail
S4.0.5: Pass
-
IE8: Pass
FF3.6: Pass
O10.51: Fail - test{foo} accepted as font name
S4.0.5: Fail - matching pair of {} bug when } closes block
-
IE8: Fail - Matching pair of [] continues to ;
FF3.6: Fail - Matching pair of [] continues to ;
O10.51: Fail - Matching pair of [] continues to ;
S4.0.5: Fail - Matching pair of [] closes at first ; Does not respect matching pair of rule
-
IE8: Fail - matched double and single quotes treated as valid inside font names
FF3.6: Pass
O10.51: Fail - matched double and single quotes treated as valid inside font names
S4.0.5: Fail - matched double and single quotes treated as valid inside font names, and open quotes closed at first ; matching pair not respected
-
IE8: Fail - matched single quotes treated as valid inside font names
FF3.6: Pass
O10.51: Fail - matched single quotes treated as valid inside font names
S4.0.5: Fail - matched single quotes treated as valid inside font names, and open quotes closed at first ; matching pair not respected
-
All: Pass
-
IE8: Pass
FF3.6: Fail - 5testfoo, testfoo 5-0, 5foo, -5, -5bar, 5_0, -5testfoo, 1996
O10.51: Fail - 5testfoo, -5testfoo, 1996
S4.0.5: Fail - 5testfoo, testfoo 5-0, 5foo, -5, -5bar, 5_0, -5testfoo, 1996
- Resolution
- ident+ syntax (proposal 1) adopted
- Status
- Closed.
- Testcases
- font-family-valid-characters-* font-family-invalid-characters-*
Issue 115
Issue 116
Issue 117
- URL
- http://lists.w3.org/Archives/Public/www-style/2009Mar/0004.html (Issues 4 and 10)
- Summary
- Vertical alignment underdefined. Testcases in URL.
- Resolution
- State that behavior described in 4a is undefined. For 4b and 4c, drop item 4 from list and add parenthetical to item 3 saying that the strut is taken into consideration. Accept 10a. For 10b, add a note saying that baseline info is found in the font and this may be further explained in CSS3.
- Status
- Closed.
Issue 119
Issue 123
Issue 124
Issue 125
- Summary
- descendants misspelled as descendents in definition of 'hidden' for 'visibility' (section 11.2)
- Resolution
- Assumed editorial.
- Status
- Closed. (Subsumed by issue 126?)
- Testcases
- n/a (editorial)
Issue 126
Issue 127
Issue 130
- Summary
- Undefined keywords mentioned in font-family
- URL
- http://lists.w3.org/Archives/Public/www-style/2009Jun/0141.html
- Proposal
- Remove 'initial' and 'default' from example list, remove 'e.g.' to make it normative, and add a sentence that says “'initial' and 'default' are reserved as keywords for future use and must be quoted when used as font names.”
- Status
- Closed.
- Testcase
- font-family-rule-010 and font-family-rule-011
Issue 131
Issue 132
Issue 133
Issue 134
Issue 135
Issue 136
Issue 141
Issue 154
Issue 156
Issue 157
Issue 158
Issue 162
- URL
- http://www.w3.org/TR/2010/WD-html-bidi-20100304/#lists
- Summary
- The side of a list bullet should depend on the directionality of its parent, not the list-item itself.
- Resolved
- No change to CSS2.1. Will accept a note showing alternate way to achieve this effect. Possibly address in CSS3.
- Status
- Closed.
- Testcase
- list-bidi-000
Issue 163
Issue 164
Issue 165
Issue 166
Issue 169
- Summary
- Normative statement about OOF elements and break opportunities should not be in note
- Proposal
- Replace sentence “A float should not introduce a line break opportunity.” with “Floated and absolutely-positioned elements do not introduce a line breaking opportunity.” from the note below below it
- Resolution
- Assumed editorial.
- Status
- Closed.
- Testcases
- n/a (editorial)
Issue 174
Issue 176
Issue 177
Issue 178
Issue 184
- Summary
- Unclear that pseudo-elements are considered a subclass of elements.
- URI
- http://lists.w3.org/Archives/Public/www-style/2010Jul/0438.html (Issue 1)
- Proposal
- Add “Pseudo-elements behave just like real elements in CSS with the exceptions described below and _elsewhere_<link to section 12.1>.” to 5.12
- Resolution
- Proposal accepted.
- Status
- Closed.
- Testcases
- n/a (editorial)
Issue 188
Issue 189
Issue 200
19 July 2007 CR Issues
Issue 1
Issue 2
Issue 3
Issue 4
- URL
- http://lists.w3.org/Archives/Public/www-style/2007Jul/0097.html
- Summary
- @charset rule prose in 4.4 requires double-quoted string (immediately followed by semicolon), but grammar allows double- or single-quoted string. Grammar is noted to be more lax than prose, so this may be ok.
- Resolution
- No change.
- Status
- Closed.
- Testcase
- at-charset-quotes-001.xht
Issue 5
Issue 6
Issue 7
Issue 8
Issue 9
Issue 10
Issue 11
Issue 12
Issue 13
Issue 14
Issue 15
Issue 16
- URL
- http://lists.w3.org/Archives/Public/www-style/2007Oct/0201.html
- Summary
- Specify image pixel mapping to CSS lengths.
- Proposal
- Append “For raster images without reliable resolution information, a size of 1 px unit per image source pixel must be assumed.” to definition of “intrinsic dimensions”.
- Resolution
- Proposal accepted.
- Status
- Closed.
- Testcases
- assumed throughout testsuite
Issue 17
Issue 18
Issue 19
Issue 20
Issue 21
Issue 22
Issue 23
Issue 24
Issue 27
Issue 28
Issue 29
- URL
- http://lists.w3.org/Archives/Public/www-style/2008Jan/0300.html
- Summary
- First paragraph of 10.3.8 confusing
- Proposal
- Replace with “In this case, Section 10.3.7 applies up through and including the constraint equation, but the rest of section 10.3.7 is replaced by the following rules:”
- Resolution
- Assumed editorial.
- Status
- Closed.
- Testcases
- n/a (editorial)
Issue 30
Issue 31
Issue 32
Issue 33
Issue 34
Issue 35
Issue 36
Issue 37
Issue 38
Issue 39
Issue 40
Issue 41
- URL
- http://lists.w3.org/Archives/Public/www-style/2008Mar/0296.html
- Summary
- Pixel values should be normatively related to device pixels
- Proposal
- Add “It is recommended that the pixel unit refer to the whole number of device pixels that best approximates the reference pixel.” to px definition
- Resolution
- Proposal accepted.
- Status
- Closed.
- Testcases
- n/a (see issue 149)
Issue 42
Issue 43
Issue 44
Issue 45
Issue 46
Issue 47
Issue 48
Issue 49
Issue 50
Issue 51
Issue 52
Issue 54
Issue 55
Issue 57
Issue 58
Issue 59
Issue 60a
Issue 62
Issue 63
Issue 64
Issue 65
- URL
- http://lists.w3.org/Archives/Public/www-style/2008Jul/0522.html
- Summary
- Section 9.2.2 says: “Several values of the 'display' property make an element inline: 'inline', 'inline-table', and 'run-in' (part of the time; see run-in boxes).” Seems to be missing 'inline-block'.
- Proposal
- Add inline-block
- Resolution
- Proposal accepted.
- Status
- Closed.
- Testcases
- n/a (editorial)
Issue 66
- URL
- http://lists.w3.org/Archives/Public/www-style/2008Jul/0473.html
- Summary
- Prose and token definition disagree on whether escapes may occur in comments
- Proposal
- In 4.1.3 prepend “Except within CSS comments” to the sentence “Any character (except a hexadecimal digit) can be escaped with a backslash to remove its special meaning.”
- Resolution
- Accepted proposal to update prose to match tokenization.
- Status
- Closed.
- Testcase
- escapes-006
Issue 67
Issue 68
Issue 70
- URL
- Summary
- Bullet points in 8.3.1 about 'overflow' not 'visible' should mention that block formatting contexts, in general, do not collapse margins with their children.
- Proposal
- In 8.3.1 change “Vertical margins of elements with 'overflow' other than 'visible'” to “Vertical margins of elements that establish new block formatting contexts (such as floats and elements with 'overflow' other than 'visible')”
- Resolution
- Proposal accepted.
- Status
- Closed.
Issue 74
Issue 76
- URL
- http://lists.w3.org/Archives/Public/www-style/2008Sep/0229.html
- Summary
- Clarify rules wrt content outside the page box
- Proposal
- When formatting content in the page model, some content may end up outside the *current* page box. For example, an element whose 'white-space' property has the value 'pre' may generate a box that is wider than the page box. *As another example,* when boxes are positioned absolutely *or relatively*, they may end up in “inconvenient” locations. For example, images may be placed on the edge of the page box or 100,000 meters below the page box.
- Resolution
- Proposal accepted.
- Status
- Closed.
- Testcases
- n/a (editorial)
Issue 77
Issue 78
- URL
- http://lists.w3.org/Archives/Public/www-style/2007Oct/0150.html
- Summary
- :before / :after description implies that :before:first-line is valid
- Proposal
- Replace “combined with” with “applied to an element having content generated using” and “including the inserted text” with “including the generated content”.
- Resolution
- Assumed editorial.
- Status
- Closed.
- Testcases
- n/a (editorial)
Issue 79
Issue 80
Issue 81
Issue 82
Issue 83
Issue 85
Issue 87
Issue 88
Issue 90
Issue 91
Issue 92
Issue 93
Issue 94
Issue 95
Issue 96
Issue 97
Issue 98
Issue 99
- URL
- http://www.w3.org/mid/495A4E7E.10305@gmail.com
- Summary
- Appendix G says: 'The two occurrences of “\377”…' but there is only one.
- Proposal
- Change this sentence and the next to singular.
- Resolution
- Assumed editorial
- Status
- Closed.
Issue 100
Issue 102
- URL
- http://lists.w3.org/Archives/Public/www-style/2009Feb/0126.html
- Summary
- Parsing of @import after garbage
- Proposal
- Only ignore @import if it follows a {non-@}-rule or a known @-rule that it is not allowed to follow.
- Resolution
- Replace “valid statement” with “non-ignored statement” in section 4.1.5
- Status
- Closed.
- Testcases
- at-import-009 at-import-010 at-import-011
Issue 103
Issue 104
Issue 105
Issue 106
Issue 108
Issue 112
Issue 113