|
1 | 1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> |
2 | 2 | <html lang="en"> |
3 | | -<!-- $Id: changes.src,v 2.121 2010-09-08 16:26:53 bbos Exp $ --> |
| 3 | +<!-- $Id: changes.src,v 2.122 2010-09-29 15:47:45 bbos Exp $ --> |
4 | 4 | <HEAD> |
5 | 5 | <TITLE>Changes</TITLE> |
6 | 6 | </HEAD> |
@@ -4219,6 +4219,68 @@ definition from “<del>[^\0-\177]</del>” to |
4219 | 4219 | <ins>[^\0-\237]</ins>”. (When CSS was first written, Unicode |
4220 | 4220 | didn't have code points U+0080 to U+009F, i.e., \200-\237 in octal.) |
4221 | 4221 |
|
| 4222 | +<!--========================== issue 129 ==========================--> |
| 4223 | + |
| 4224 | +<h3 id="t.4.1.1a"><a |
| 4225 | +href="/TR/2009/CR-CSS2-20090908/syndata.html#tokenization"> |
| 4226 | +Section 4.1.1 Tokenization</a></h3> |
| 4227 | + |
| 4228 | +<p><span class=date>[2010-09-29]</span> The tokenizer has been |
| 4229 | +modified so that it can be implemented as a state machine without |
| 4230 | +back-up (e.g., with Lex). This changes the meaning of an input of the |
| 4231 | +form “url(…(…)…)”, i.e., input that |
| 4232 | +starts like a URI token but then contains a parenthesis (which is not |
| 4233 | +allowed in a URI token). Previously, such input was re-parsed to yield |
| 4234 | +a FUNCTION token followed by other things; now it yields a BAD_URI |
| 4235 | +token. Given that CSS has never used a FUNCTION token of the form |
| 4236 | +“url(” this should not affect any existing CSS style |
| 4237 | +sheets. |
| 4238 | + |
| 4239 | +<p>A non-normative section has been added to appendix G with an |
| 4240 | +explanation of how to make a tokenizer without back-up. |
| 4241 | + |
| 4242 | +<!--========================== issue 139 ==========================--> |
| 4243 | + |
| 4244 | +<h3 id="t.4.1.1b"><a |
| 4245 | +href="/TR/2009/CR-CSS2-20090908/syndata.html#tokenization"> |
| 4246 | +Section 4.1.1 Tokenization</a></h3> |
| 4247 | + |
| 4248 | +<p><span class=date>[2010-09-29]</span> The definition of the URI |
| 4249 | +token was ambiguous: it allowed a backslash to be either parsed on its |
| 4250 | +own or as part of an escape. A backslash in a URI token must always be |
| 4251 | +interpreted as part of an escape. |
| 4252 | + |
| 4253 | +<!--========================== issue 140 ==========================--> |
| 4254 | + |
| 4255 | +<h3 id="t.4.1.1c"><a |
| 4256 | +href="/TR/2009/CR-CSS2-20090908/syndata.html#tokenization"> |
| 4257 | +Section 4.1.1 Tokenization</a></h3> |
| 4258 | + |
| 4259 | +<p><span class=date>[2010-09-29]</span> Error handling for illegal |
| 4260 | +tokens (braces, at-keywords, and SGML comment tokens) inside |
| 4261 | +parenthesized expressions was not well defined. Change the production |
| 4262 | +for “any” as follows |
| 4263 | + |
| 4264 | +<blockquote> |
| 4265 | +<pre> |
| 4266 | +any : [ IDENT | NUMBER | PERCENTAGE | DIMENSION | STRING |
| 4267 | + | DELIM | URI | HASH | UNICODE-RANGE | INCLUDES |
| 4268 | + | DASHMATCH | ':' | FUNCTION S* <ins>[</ins>any<ins>|unsused]</ins>* ')' |
| 4269 | + | '(' S* <ins>[</ins>any<ins>|unused]</ins>* ')' | '[' S* <ins>[</ins>any<ins>|unused]</ins>* ']' |
| 4270 | + ] S*; |
| 4271 | +<ins>unused : block | ATKEYWORD S* | ';' S* | CDO S* | CDC S*;</ins> |
| 4272 | +</pre> |
| 4273 | +</blockquote> |
| 4274 | + |
| 4275 | +<p>and add the following explanation: |
| 4276 | + |
| 4277 | +<blockquote> |
| 4278 | +<p><ins>The "unused" production is not used in CSS and will not be |
| 4279 | +used by any future extension. It is included here only to help with |
| 4280 | +error handling. (See 4.2 "Rules for handling parsing |
| 4281 | +errors.")</ins> |
| 4282 | +</blockquote> |
| 4283 | + |
4222 | 4284 | <!--========================== issue 136 ==========================--> |
4223 | 4285 |
|
4224 | 4286 | <h3 id="t.4.1.2.2"><a |
@@ -4322,6 +4384,39 @@ not apply within a URI value. Therefore comments are not allowed |
4322 | 4384 | within a URI value.</ins> |
4323 | 4385 | </blockquote> |
4324 | 4386 |
|
| 4387 | +<!--========================== issue 143 ==========================--> |
| 4388 | + |
| 4389 | +<h3 id="t.5.8.2"><a |
| 4390 | +href="/TR/2009/CR-CSS2-20090908/selector.html#default-attrs"> |
| 4391 | +Section 5.8.2 Default attribute values in DTDs</a></h3> |
| 4392 | + |
| 4393 | +<p><span class=date>[2010-09-29]</span> Clarify what is meant by |
| 4394 | +“is not required”: |
| 4395 | + |
| 4396 | +<blockquote> |
| 4397 | +<p>More precisely, a UA <ins>may, but</ins> is <em>not</em> required |
| 4398 | +to<ins>,</ins> read an "external subset" of the DTD but <em>is</em> |
| 4399 | +required to look for default attribute values in the document's |
| 4400 | +"internal subset." (See [XML10] for definitions of these subsets.) |
| 4401 | +<ins>Depending on the UA, a default attribute value defined in the external |
| 4402 | +subset of the DTD might or might not appear in the document tree.</ins> |
| 4403 | + |
| 4404 | +<p>A UA that recognizes an XML namespace [XMLNAMESPACES] <ins>may, |
| 4405 | +but</ins> is not required to<ins>,</ins> use its knowledge of that |
| 4406 | +namespace to treat default attribute values as if they were present in |
| 4407 | +the document. (E.g., an XHTML UA is not required to use its built-in |
| 4408 | +knowledge of the XHTML DTD.) |
| 4409 | +</blockquote> |
| 4410 | + |
| 4411 | +<p>and: |
| 4412 | + |
| 4413 | +<blockquote> |
| 4414 | +<p>the first rule <del>will</del> <ins>might</ins> not match elements |
| 4415 | +whose "notation" attribute is set by default, i.e., not set |
| 4416 | +explicitly. To catch all cases, the attribute selector for the default |
| 4417 | +value must be dropped: |
| 4418 | +</blockquote> |
| 4419 | + |
4325 | 4420 | <!--========================== issue 175 ==========================--> |
4326 | 4421 |
|
4327 | 4422 | <h3 id="t.5.11.4"><a |
@@ -4487,6 +4582,41 @@ mark-up. Change it to use P and SPAN elements instead of BODY and P. |
4487 | 4582 | <p><span class=date>[2010-08-06]</span> Also clarify that “block |
4488 | 4583 | box” only refers to boxes in the same flow. |
4489 | 4584 |
|
| 4585 | +<!--========================== issue 137 =========================--> |
| 4586 | + |
| 4587 | +<h3 id="t.9.2.1.1a"><a |
| 4588 | +href="/TR/2009/CR-CSS2-20090908/visuren.html#anonymous-block-level"> |
| 4589 | +Section 9.2.1.1 Anonymous block boxes</a></h3> |
| 4590 | + |
| 4591 | +<p><span class=date>[2010-09-29]</span> Percentage values that refer |
| 4592 | +to dimensions of parent boxes ignore any intervening anonymous |
| 4593 | +boxes. Add this paragraph: |
| 4594 | + |
| 4595 | +<blockquote> |
| 4596 | +<p><ins>Anonymous block boxes are ignored when resolving percentage |
| 4597 | +values that would refer to it: the closest non-anonymous ancestor box |
| 4598 | +is used instead. For example, if the child of the anonymous block box |
| 4599 | +inside the DIV above needs to know the height of its containing block |
| 4600 | +to resolve a percentage height, then it will use the height of the |
| 4601 | +containing block formed by the DIV, not of the anonymous block |
| 4602 | +box.</ins> |
| 4603 | +</blockquote> |
| 4604 | + |
| 4605 | +<!--========================== issue 138 =========================--> |
| 4606 | + |
| 4607 | +<h3 id="t.9.2.1.1b"><a |
| 4608 | +href="/TR/2009/CR-CSS2-20090908/visuren.html#anonymous-block-level"> |
| 4609 | +Section 9.2.1.1 Anonymous block boxes</a></h3> |
| 4610 | + |
| 4611 | +<p><span class=date>[2010-09-29]</span> Clarify the wording: |
| 4612 | + |
| 4613 | +<blockquote> |
| 4614 | +<p>When an inline box contains an in-flow block box […] When |
| 4615 | +such an inline box is affected by relative positioning, the relative |
| 4616 | +positioning also affects the block-level box <ins>contained in the |
| 4617 | +block box</ins>. |
| 4618 | +</blockquote> |
| 4619 | + |
4490 | 4620 | <!--========================== issue 120 ==========================--> |
4491 | 4621 |
|
4492 | 4622 | <h3 id="t.9.2.2"><a |
@@ -4951,7 +5081,7 @@ and “preceding”: |
4951 | 5081 | <blockquote> |
4952 | 5082 | <p>In certain cases (see <del>the preceding sections</del> |
4953 | 5083 | <ins>e.g., sections 10.6.4 and 10.6.6</ins>), the height of an element |
4954 | | -is computed as follows: |
| 5084 | +that establishes a block formatting context is computed as follows: |
4955 | 5085 |
|
4956 | 5086 | <p>[…] |
4957 | 5087 |
|
|
0 commit comments