forked from w3c/csswg-drafts
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathchanges.src
More file actions
1014 lines (735 loc) · 35.4 KB
/
Copy pathchanges.src
File metadata and controls
1014 lines (735 loc) · 35.4 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en">
<!-- $Id: changes.src,v 2.35 2003-01-22 18:38:15 bbos Exp $ -->
<HEAD>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<TITLE>Appendix B: Changes</TITLE>
</HEAD>
<BODY>
<H1>Changes</H1>
<P><em>This appendix is informative, not normative.</em></P>
<P>CSS 2.1 is an updated version of CSS2. The changes between the
CSS2 specification (see [[CSS2]]) and this specification fall into
five groups: known errors, typographical errors, clarifications,
changes and additions. Typographical errors are not listed here.</P>
<h2><a name="new">Additional property values</a></h2>
<h3 id="s-4-3-5"><a href="syndata.html#color-units">Section 4.3.5
Colors</a></h3>
<p>New color value: 'orange'
<h3 id="s-9-2-4"><a href="visuren.html#propdef-display">Section 9.2.4
The 'display' property</a></h3>
<p>New 'display' value: 'inline-block'
<h3 id="s-18-1"><a href="ui.html#propdef-cursor">Section 18.1 Cursors:
the 'cursor' property</a></h3>
<p>New 'cursor' value: 'progress'
<h3 id="s-16-6"><a href="text.html#propdef-white-space">Section 16.6
Whitespace: the 'white-space' property</a></h3>
<p>New 'white-space' values: 'pre-wrap' and 'pre-line'
<h2><a name="changes">Changes</a></h2>
<h3 id="s-3-2"><a href="conform.html#conformance">Section 3.2
Conformance</a></h3>
<p>Support for user style sheets is now required (in most cases),
rather than just recommended.
<h3 id="s-6-4-3"><a href="cascade.html#specificity">Section 6.4.3
Calculating a selector's specificity</a></h3>
<p>The "style" attribute now has a higher specificity than any style
rule.
<h3 id="s-6-4-4"><a href="cascade.html#q12">Section 6.4.4 Precedence
of non-CSS presentational hints</a></h3>
<p>"Non-CSS presentational hints" no longer exist, with the exception
of a small set of attributes in HTML.
<h3 id="visuren"><a href="visuren.html">Chapter 9 Visual formatting
model</a></h3>
<p>The value 'compact' for 'display' does not exist in CSS 2.1.
<h3 id="s-10-3-7"><a
href="visudet.html#abs-non-replaced-width">Section 10.3.7 Absolutely
positioned, non-replaced elements</a></h3>
<p>Absolutely positioned elements can now "shrink-wrap" their
contents:
<p>When both 'width' and 'right' (or 'width' and 'left') are 'auto',
the element's computed width is the width of the contents (using an
algorithm similar to that for table cells) and then 'right' (or
'left') is solved. CSS2 incorrectly said that 'right' (or 'left') was
set to 0 in that case, and then width was solved.
<h3 id="s-10-6-4"><a
href="visudet.html#abs-non-replaced-height">Section 10.6.4 Absolutely
positioned, non-replaced elements</a></h3>
<p>Like normal-flow block-level elements, absolutely positioned
elements by default take on the height of their contents
("shrink-wrap"). If 'height' and 'bottom' are both 'auto', the
computed value of 'height' is set to the height of the contents and
then 'bottom' is solved. CSS2 incorrectly said the reverse: 'bottom'
was set to 0 and then height was solved.
<h3 id="x88"><a href="visufx.html#clipping">Section 11.1.2 Clipping:
the 'clip' property</a></h3>
<p>While CSS2 specified that values of "rect()" give offsets from the
respective sides of the box, current implementations interpret values
with respect to the top and left edges for <em>all</em> four values
(top, right, bottom, and left). This is now the correct
interpretation.
<h3 id="s-17-4-1"><a href="tables.html#q6">17.4.1 Caption position
and alignment</a></h3>
<p>The 'left' and 'right' values on 'caption-side' have been removed.
<h3 id="s-17-5-4"><a href="tables.html#column-alignment">17.5.4
Horizontal alignment in a column</a></h3>
<p>The <string> value for 'text-align' is not part of
CSS 2.1.
<h3 id="s-17-6"><a href="tables.html#borders">Section 17.6
Borders</a></h3>
<p>Several popular browsers assume an initial value for
'border-collapse' of 'separate' rather than 'collapse' or exhibit
behavior that is close to that value, even if they do not actually
implement the CSS table model. 'Separate' is now the initial value.
<h3 id="s-12"><a href="generate.html">Chapter 12 Generated content,
automatic numbering, and lists</a></h3>
<p>The 'marker' value for 'display' does not exist in CSS 2.1
<h3 id="s-12-2"><a href="generate.html#propdef-content">Section 12.2
The 'content' property</a></h3>
<p>The '<uri>' value is dropped.
<h3 id="page"><a href="page.html">Chapter 13 Paged media</a></h3>
<p>The 'size', 'marks' and 'page' properties are not in CSS 2.1.
<h3 id="s-15"><a href="fonts.html">Chapter 15 Fonts</a></h3>
<p>The 'font-stretch' and 'font-size-adjust' properties don't exist in
CSS 2.1.
<p>Font descriptors and the '@font-face' declaration don't exist in
CSS 2.1.
<h3 id="text"><a href="text.html">Chapter 16 Text</a></h3>
<p>The 'text-shadow' property is not in CSS 2.1.
<h3 id="a-a"><a href="aural.html">Appendix A. Aural style
sheets</a></h3>
<p>Chapter 19 on aural style sheets has become appendix A and is not
normative in CSS 2.1. Related units (deg, grad, rad, ms, s, Hz,
kHz) are also moved to this appendix, as is the 'speak-header'
property from the "tables" chapter.
<h3 id="other">Other</h3>
<p>The former informative appendix C, "Implementation and
performance notes for fonts," is left out of CSS 2.1.
<h2><a name="known-errors">Errors</a></h2>
<h3 id="x1">Shorthand properties</h3>
<p>Shorthand properties take a list of subproperty values <em>or</em>
the value 'inherit'. One cannot mix 'inherit' with other subproperty
values as it would not be possible to specify the subproperty to which
'inherit' applied. The definitions of a number of shorthand properties
did not enforce this rule: 'border-top', 'border-right',
'border-bottom', 'border-left', 'border', 'background', 'font',
'list-style', 'cue', and 'outline'.
<h3 id="x3"><a href="syndata.html#tokenization">Section 4.1.1</a> (and
<a href="grammar.html#q2">G2</a>)</h3>
<ul>
<li>The "nmchar" token also allows the range "A-Z".
<li>In the rule for "any" (in the core syntax), changed "FUNCTION"
to "FUNCTION any* ')'".
</ul>
<p id="underscore">The underscore character
("_") is allowed in identifiers. The definitions of the lexical
macros "nmstart" and "nmchar" now include it.
<h3 id="x4"><a href="syndata.html#q4">4.1.3 Characters and case</a></h3>
<p>In the third bullet, added to point 1:
<blockquote>
<p>1.with a space (or other whitespace character): "\26 B" ("&B")
</blockquote>
<p>the following text: "In this case, user agents should treat a
"CR/LF" pair (13/10) as a single whitespace character."
<p>The underscore is
allowed in identifiers. Changed "In CSS2, identifiers [...] can contain
only the characters [A-Za-z0-9] and ISO 10646 characters 161 and
higher, plus the hyphen (-)" to:
<blockquote><p>In CSS2, identifiers [...] contain only the characters
[A-Za-z0-9] and ISO 10646 characters 161 and higher, plus the hyphen
(-) and the underscore (_)</p></blockquote>
<h3 id="x5"><a href="syndata.html#values">Section 4.3 (Double sign problem)</a></h3>
<p>Several values described in subsections of this section
incorrectly allowed two "+" or "-" signs at their beginnings.
<h3 id="s-4-3-2"><a href="syndata.html#length-units">Section 4.3.2
Lengths</a></h3>
<p>The suggested reference
pixel is based on a <ins>96 dpi</ins> device, not 90 dpi.
The visual angle is thus about <ins>0.0213 degrees</ins> instead of
0.0227, and a pixel at arm's length is about <ins>0.26 mm</ins>
instead of 0.28
<h3 id="x6"><a href="syndata.html#color-units">Section 4.3.6</a></h3>
<p>Deleted the comments about range
restriction after the following examples:
<pre>
em { color: rgb(255,0,0) }
em { color: rgb(100%, 0%, 0%) }
</pre>
<h3 id="x7"><a href="selector.html#q2">5.10 Pseudo-elements and pseudo-classes</a></h3>
<p>In the second bullet, the following sentence was incomplete: "The
exception is ':first-child', which can be deduced from the document
tree." The ':lang()' pseudo-class can be deduced
from the document in some cases.
<h3 id="x8"><a href="box.html#mpb-examples">8.2 Example of margins, padding, and borders</a></h3>
<p>The colors in the example HTML did not match the colors in the
image.
<h3 id="s-8-5-2"><a href="box.html#border-color-properties">Section
8.5.2 Border color: 'border-top-color', 'border-right-color',
'border-bottom-color', 'border-left-color', and
'border-color'</a></h3>
<p>The value 'transparent' is
also allowed on 'border-top-color', 'border-right-color', etc. Changed
the line "Value: <color> | inherit" to
<blockquote><p>Value: <color> | transparent | inherit</blockquote>
<h3 id="x2"><a href="box.html#padding-properties">Section 8.4 Padding properties</a></h3>
<p>The five properties related to padding ('padding', 'padding-top',
'padding-right', 'padding-bottom', and 'padding-left') now say that
they don't apply to table rows, row groups, header groups, footer
groups, columns, and column groups.
<h3 id="x9"><a href="box.html#border-style-properties">8.5.3 Border
style</a></h3>
<p>Changed the sentence "The color of borders drawn for values of
'groove', 'ridge', 'inset', and 'outset' depends on the element's
'color' property" to
<blockquote><p>The color of borders drawn for values of 'groove',
'ridge', 'inset', and 'outset' should be based on the element's
'border-color' property, but UAs may choose their own algorithm to
calculate the actual colors used. For instance, if the 'border-color'
has the value 'silver', then a UA could use a gradient of colors from
white to dark gray to indicate a sloping border.</blockquote>
<h3 id="s-8-5-4"><a
href="box.html#border-shorthand-properties">Section 8.5.4 Border
shorthand properties: 'border-top', 'border-bottom', 'border-right',
'border-left', and 'border'</a></h3>
<p>Changed <'border-top-width'> to <border-width> as the first
value option for 'border-top', 'border-right', 'border-bottom',
and 'border-left', and changed <'border-style'> to <border-style>.
For 'border', changed <'border-width'>
to <border-width> and
<'border-style'> to <border-style>.
<p>The value 'transparent' is
also allowed on 'border-top', 'border-bottom', 'border-right',
'border-left', and 'border'.
<p>Changed the two lines "Value: [ <'border-top-width'> ||
<'border-style'> || <color> | inherit" to
<blockquote><p>Value: [ <border-top-width> || <border-style>
|| [<color> | transparent] | inherit</blockquote>
<h3 id="x10"><a href="box.html#value-def-border-width">8.5.4 Border shorthand properties: 'border-top', 'border-bottom', 'border-right', 'border-left', and
'border'</a></h3>
<p>Changed <'border-top-width'> to <border-width> as the first
value option for 'border-top', 'border-right', 'border-bottom',
and 'border-left', and changed <'border-style'> to <border-style>.
For 'border', changed <'border-width'>
to <border-width> and
<'border-style'> to <border-style>.
<h3 id="x11"><a href="visuren.html#choose-position">Section 9.3.1</a></h3>
<p>The definition of the value 'static' now
says that the properties 'top', 'right', 'bottom', and 'left'
do not apply.
<h3 id="x12"><a href="visuren.html#position-props">Section 9.3.2</a></h3>
<p>The properties 'top', 'right', 'bottom', and 'left', incorrectly
referred to offsets with respect to a box's content edge. The proper edge
is the margin edge. Thus, for 'top', the description now reads:
"This property specifies how far a box's top margin edge is offset
below the top edge of the box's containing block."
<h3 id="x13"><a href="visuren.html#relative-positioning">Section 9.4.3</a></h3>
<p>In the first sentence, added to the end of
"Once a box has been laid out according to the normal flow"
the words "or floated,".
<h3 id="s-9-7"><a href="visuren.html#q24">Section
9.7 Relationships between 'display', 'position', and 'float'</a></h3>
<p>If an element floats, the
'display' property is set to a block-level value, but not necessarily
'block'. In bullet 3, changed "Otherwise, if 'float' has a value other
than 'none', 'display' is set to 'block' and the box is floated" to a
table with the proper computed values.
<h3 id="x14"><a href="visudet.html#q5">Section 10.3.2
Inline, replaced elements</a> (and 10.3.4, 10.3.6, and 10.3.8)</h3>
<p>Changed:</p>
<blockquote>
<p> A specified value of 'auto' for 'width' gives the element's intrinsic
width as the computed value.
</blockquote>
<p>to:</p>
<blockquote>
<p> If 'width' has a specified value of 'auto' and 'height' also has a
specified value of 'auto', the element's intrinsic width is the
computed value of 'width'. If 'width' has a specified value of
'auto' and 'height' has some other specified value, then the computed
value of 'width' is
(intrinsic width) * ( (computed height) / (intrinsic height) ).
</blockquote>
<h3 id="x15"><a href="visudet.html#q6">Section 10.3.3</a></h3>
<p>In the last sentence of the paragraph following the equation
("If the value of 'direction' is 'ltr', this happens to
'margin-left' instead") substituted 'rtl' for 'ltr'.
<h3 id="x16"><a href="visudet.html#q16">Section 10.6.2
Inline, replaced elements ...</a> (and 10.6.5)</h3>
<p>Changed:</p>
<blockquote>
<p> If 'height' is 'auto', the computed value
is the intrinsic height.
</blockquote>
<p>to:</p>
<blockquote>
<p> If 'height' has a specified value of 'auto' and 'width' also has a
specified value of 'auto', the element's intrinsic height is the
computed value of 'height'. If 'height' has a specified value of
'auto' and 'width' has some other specified value, then the computed
value of 'height' is
(intrinsic height) * ( (computed width) / (intrinsic width) ).
</blockquote>
<h3 id="x17"><a href="visudet.html#q17">Section 10.6.3</a></h3>
<p>The height calculation for block-level, non-replaced elements in
normal flow, and floating, non-replaced elements was not quite
correct. It now takes into account the case when margins do not
collapse, due to the presence of a padding or border.
<h3 id="x18"><a href="visufx.html#overflow">Section 11.1.1</a></h3>
<p>The example of a DIV element containing a BLOCKQUOTE containing
another DIV was not rendered correctly. The first style rule applied
to both DIVs, so the second DIV box should have been rendered with a
red border as well. The second DIV has now been changed to a CITE,
which doesn't have a red border.
<h3 id="s-11-2"><a href="visufx.html#propdef-visibility">11.2
Visibility: the 'visibility' property</a></h3>
<p>Changed "initial" and
"inherited" to:
<blockquote><p>
<em>Initial:</em> visible<br>
<em>Inherited:</em> yes
</blockquote>
<p>This has the same effect as the original definition, but removes
the undefined state of the root element (which was a problem for DOM
implementations).
<h3 id="x20"><a href="generate.html#lists">12.6.2 Lists</a></h3>
<p>Under the 'list-style' property, the example:</p>
<pre>
ul > ul { list-style: circle outside } /* Any UL child of a UL */
</pre>
<p>could never match valid HTML markup (since a UL element
cannot be a child of another UL element). An LI has been inserted in
between.
<h3 id="x22"><a href="fonts.html#generic-font-families">Section 15.2.6</a></h3>
<p>'Totum' and 'Kodic' is not a 'serif' but 'sans-serif'. 'pathang' is
not a 'sans-serif' but 'serif'.
<h3 id="x23"><a href="fonts.html#algorithm">Section 15.5</a></h3>
<p>In bullet 2, changed "the UA uses the 'font-family' descriptor"
to "the UA uses the 'font-family' property".
<p>In bullet 6, changed "steps 3, 4 and 5" to
"steps 2, 3, 4 and 5".
<h3 id="s-16-6a"><a href="text.html#propdef-white-space">Section 16.6
Whitespace: the 'white-space' property</a></h3>
<p>The 'white-space' property
applies to <em>all</em> elements, not just block-level elements.
<h3 id="x24"><a href="tables.html#q2">Section 17.2 The CSS table
model</a></h3>
<p>In the definition of <strong>table-header-group</strong>, changed
"footer" to "header" in "Print user agents may repeat footer rows on
each page spanned by a table."
<h3 id="x25"><a href="tables.html#anonymous-boxes">17.2.1 Anonymous table objects </a></h3>
<p>Moved the first bullet text to the prose before the list of
generation rules and added missing rules.
<h3 id="x26"><a href="tables.html#q7">17.5 Visual layout of table
contents</a></h3>
<p>The following note:</p>
<blockquote>
<p><strong>Note.</strong> Table cells may be relatively and absolutely positioned, but this is not recommended: positioning and floating remove a
box from the flow, affecting table alignment.
</p>
</blockquote>
<p>has been amended as follows:</p>
<blockquote>
<p><strong>Note.</strong> Table cells may be
positioned, but this is not recommended: absolute and fixed
positioning, as well as floating, remove a box from the flow, affecting
table size.
</p>
</blockquote>
<h3 id="x27"><a href="tables.html#q7">17.5 Visual layout of table
contents</a></h3>
<p>Changed:
<blockquote>
<p>Like other elements of the document language, internal table
elements generate rectangular boxes with content, padding, and
borders. They do not have margins, however.
</blockquote>
<p>to:
<blockquote>
<p>Like other elements of the document language, internal table
elements generate rectangular boxes with content and
borders. Cells have padding as well. Internal table elements do not
have margins.
</blockquote>
<h3 id="s-17-5-1"><a href="tables.html#table-layers">Section 17.5.1
Table layers and transparency</a></h3>
<p>The rows and columns only cover the whole table in the collapsed
borders model, not in the separated borders model. The points 2, 3, 4
and 5 have been corrected to define the area covered by rows, columns,
row groups and column groups in terms of the cells they cover.
<h3 id="x28"><a href="tables.html#separated-borders">Section 17.6.1 The
separated borders model</a></h3>
<p>In the image, changed "cell-spacing" to "border-spacing".
<h3 id="underscore2"><a href="grammar.html#q2">Appendix D.2 Lexical
scanner</a></h3>
<p>The underscore character
("_") is be allowed in identifiers. The definitions of the lexical
macros "nmstart" and "nmchar" have been fixed.
<p>Note that the tokenizer is case-insensitive, so uppercase A-Z is
matched as well.
<p>(Same change in section 4.1.1, see <a href="#underscore">above</a>.)
<h2><a name="clarifications">Clarifications</a></h2>
<h3 id="s-2-2"><a
href="http://www.w3.org/TR/REC-CSS2/intro.html#q2">2.2 A brief CSS2
tutorial for XML</a></h3>
<p>The specification for the <a
href="http://www.w3.org/1999/06/REC-xml-stylesheet-19990629/">XML
style sheet PI</a>
was written after CSS2 was finalized. The first line of the full XML
example should not have been be <code><?XML:stylesheet type="text/css"
href="bach.css"?></code>, but
<pre><?xml-stylesheet type="text/css" href="bach.css"?></pre>
<h3 id="x54"><a href="selector.html#syndata.html#tokenization">Section 4.1.1</a></h3>
<p>DELIM should not have included single or double quote. Refer also
to section 4.1.6 on strings, which must have matching single or
double quotes around them.
<h3 id="x55"><a href="selector.html#descendant-selectors">Section 5.5</a></h3>
<p>Near the end of the section, the text 'Note the whitespace on
either side of the "*"' was misleading. The note was not meant to
imply that whitespace is required on both sides of the "*" (since the
grammar does not require it in this case) but that one may use
whitespace in this case.
<h3 id="x56"><a href="selector.html#id-selectors">Section 5.9 ID selectors</a></h3>
<p>The word "precedence" in the last but one paragraph should have been
"specificity."
<h3 id="s-5-12-1"><a href="selector.html#first-line-pseudo">Section
5.12.1 The :first-line pseudo-element</a></h3>
<p>Added some clarifications at the end of the section about the
fictional tag sequence in the case of nested block-level elements
<h3 id="x57"><a href="cascade.html#value-def-inherit">Section 6.2.1</a></h3>
<p>The 'inherit' value causes the properties value to be
inherited. This applies even to properties for which values
do not otherwise inherit.
<h3 id="x58"><a href="cascade.html#cascade">6.4 The Cascade
</a></h3>
<p>Changed "Rules specified in a given style sheet
override rules imported from other style sheets." to
"Rules specified in a given style sheet
override rules of the same weight imported from other style sheets."
</p>
<h3 id="x59"><a href="cascade.html#specificity">Section 6.4.3 Calculating a
selector's specificity</a></h3>
<p>Added a note:
<blockquote><p>The specificity is based only on the form of the selector.
In particular, a selector of the form "<code>[id=p33]</code>" is
counted as an attribute selector (a=0, b=1, c=0), even if the
<code>id</code> attribute is defined as an "ID" in the source
document's DTD.
</blockquote>
<h3 id="s-7-3"><a href="media.html#media-types">Section 7.3 Recognized
media types</a></h3>
<p>Text has been added to clarify that media types are mutually
exclusive.
<h3 id="x60"><a href="box.html#box-dimensions">Section 8.1</a></h3>
<ul>
<li>From the definition of "padding edge", deleted the sentence "The
padding edge of a box defines the edges of the containing block
established by the box." For information about containing
blocks, consult <a href="visudet.html#containing-block-details">
Section 10.1</a>.
<li>Border backgrounds are not specified by border properties. Changed
the last paragraph of 8.1 to:
<blockquote>
<p>The background style of the content, padding, and border areas of a
box is specified by the <span
class="propinst-background">'background'</span> property of the
generating element. Margin backgrounds are always transparent.
</blockquote>
</ul>
<h3 id="x61"><a href="box.html#collapsing-margins">Section 8.3.1</a></h3>
<p>Added this clarifying note to the first bullet of the explanation
of vertical collapsing of margins:</p>
<blockquote>
<p><strong>Note.</strong> Adjoining boxes may be generated by
elements that are not related as siblings or ancestors.
</blockquote>
<h3 id="x62"><a href="visuren.html#inline-formatting">Section 9.4.2</a></h3>
<p>The statement "When an inline box is split, margins, borders, and
padding have no visual effect where the split occurs." has been
generalized. Margins, borders, and padding have no visual effect
where one or more splits occur.
<h3 id="x63"><a href="visuren.html#relative-positioning">Section 9.4.3</a></h3>
<p>Relatively positioned boxes do not always establish new containing
blocks. Changed the second paragraph accordingly.
<p>Added clarifying text and an example about the 'left',
'right', 'top' and 'bottom' properties for relative positioning.
<h3 id="x64"><a href="visuren.html#direction">Section 9.10</a></h3>
<p>In this sentence of the last paragraph:</p>
<blockquote>
<p>Conforming HTML user agents may therefore ignore the 'direction'
and 'unicode-bidi' properties in author and user style sheets.
</blockquote>
<p>the word "ignore" meant that if a 'unicode-bidi' or 'direction'
value conflicts with the HTML 4.0 "dir" attribute value, then user
agents may choose to use the "dir" value rather than the CSS
properties.
<p>User agents are not required to support the <span
class="propinst-direction">'direction'</span> and <span
class="propinst-unicode-bidi">'unicode-bidi'</span> properties to
conform to CSS2 unless they support bi-directional text rendering
(except for the case of HTML 4.0 as noted above).
<p>The sentence has been rewritten to be clearer.
<h3 id="s-10-3-3"><a href="visudet.html#q6">10.3.3 Block-level,
non-replaced elements in normal flow</a></h3>
<p>Added the following note at
the end of the section:
<blockquote><p>Note that 'width' may not be greater than 'max-width' and
not less than 'min-width'. In particular, it may not be negative. See
the rules in section 10.4 below.</blockquote>
<h3 id="s-10-5"><a href="visudet.html#the-height-property">Section
10.5 Content height: the 'height' property</a></h3>
<p>The UA is free to chose the containing block for the root element
(see 10.1), therefore this sentence has been added as a suggestion:
<blockquote>
<p>A UA may compute a percentage height on the root element relative
to the viewport.
</blockquote>
<h3 id="x65"><a href="visudet.html#propdef-line-height">Section 10.8.1</a></h3>
<p>Clarified this paragraph:
<blockquote>
<p>Note that replaced elements have a 'font-size' and a 'line-height'
property, even if they are not used directly to determine the height
of the box. The 'font-size' is, however, used to define the 'em' and
'ex' units, and the 'line-height' has a role in the 'vertical-align'
property.
</blockquote>
<p>as follows:
<blockquote>
<p>Note that replaced elements have a <span
class="propinst-font-size">'font-size'</span> and a <span
class="propinst-line-height">'line-height'</span> property, even if
they are not used directly to determine the height of the box: 'em'
and 'ex' values are relative to values of <span
class="propinst-font-size">'font-size'</span> and percentage values
for <span class="propinst-vertical-align">'vertical-align'</span> are
relative to values of <span
class="propinst-line-height">'line-height'</span>.
</blockquote>
<p>Under 'line-height', after
the sentence "If the property is set on a block-level element whose
content is composed of inline-level elements, it specifies the
<em>minimal</em> height of each generated inline box," added the
following clarification:
<blockquote><p>The minimum height consist of a minimum height above
the block's baseline and a minimum depth below it, exactly as if each
line box starts with a zero-width inline box with the block's font and
line height properties (what T<sub>E</sub>X calls a
"strut").</blockquote>
<h3 id="x66"><a href="visufx.html#overflow-clipping">Section 11.1</a></h3>
<p>Clarifications to the last two bullets on when overflow may
occur:</p>
<ul>
<li>A descendent box is positioned
absolutely partly outside of the box.
<li>A descendent box has negative margins, causing it
to be positioned partly outside the box.
</ul>
<h3 id="x67"><a href="visufx.html#overflow">Section 11.1.1</a></h3>
<p>Removed 'projection' from this sentence under the value 'scroll'
<blockquote>
<p>
When this value is specified and the target medium is 'print' or 'projection', overflowing content should be printed.
</p>
</blockquote>
<h3 id="x68"><a href="visufx.html#clipping">Section 11.1.2</a></h3>
<p>Values of "rect()" should be separated by commas. Thus, the
definition of <shape> now starts:</p>
<blockquote>
<p>In CSS2, the only valid <shape> value is: rect (<top>, <right>, <bottom>,
<left>) ...
</blockquote>
<p>Due to this ambiguity, user agents may support separation of
offsets in "rect()" with or without commas.
<h3 id="x69"><a href="generate.html#before-after-content">12.1 The
:before and :after pseudo-elements</a></h3>
<p>Clarification to the following lines:</p>
<blockquote>
<p>The :before and :after pseudo-elements elements allow values of the
'display' property as follows:
<ul>
<li>If the subject of the
selector is a block-level
element, allowed values are 'none', 'inline' and 'block'.
If the value of the pseudo-element's
<span class="propinst-display">'display'</span> property
has any other value, the pseudo-element will behave as if its value
were 'block'.
<li>If the subject of the
selector is an inline-level
element, allowed values are 'none' and 'inline'.
If the value of the pseudo-element's
<span class="propinst-display">'display'</span> property
has any other value, the pseudo-element will behave as if its value
were 'inline'.
</ul>
</blockquote>
<h3 id="s-12-4-2">Section 12.4.2 Inserting quotes with the 'content'
property</h3>
<p>Added the following sentence
at the end of the 2nd paragraph:
<blockquote><p>A 'close-quote' that would make the depth negative is
in error and is ignored: the depth stays at 0 and no quote mark is
rendered (although the rest of the 'content' property's value is still
inserted).
</blockquote>
<h3 id="x70"><a href="generate.html#lists">Lists 12.6.2</a></h3>
<p>To clarify Hebrew numbering, added
"(Alef,
Bet, ... Tet Vav, Tet Zayin, ... Yod Tet, Kaf ...)".
<h3 id="x71"><a href="colors.html#q2">14.2 The background</a></h3>
<p>Second sentence: "In terms of the box model, 'background' refers to
the background of the content and the padding areas" now also
mentions the border area. (See also <a href="#x60">errata to section
8.1</a> above.) Thus:
<blockquote>
<p>In terms of the box model, "background" refers to the background of
the content, padding and border areas.
</blockquote>
<p>In the fourth paragraph, added to the end of "User agents should
observe the following precedence rules to fill in the background"
the following words: "of the canvas".
<h3 id="x72"><a href="colors.html#propdef-background-attachment">14.2.1
Background properties</a></h3>
<p>Added this note after the first paragraph after 'background-attachment':
<blockquote><p>Note that there is only <em>one</em> viewport per
document. I.e., even if an element has a scrolling mechanism (see
'overflow'), a 'fixed' background doesn't move with it.</blockquote>
<p>Under 'background-repeat',
the sentence "All tiling covers the content and padding areas [...]"
has been corrected to
<blockquote><p>"All tiling covers the content, padding <ins>and
border</ins> areas [...]".</blockquote>
<p>Under 'background-attachment',
the sentence "Even if the image is fixed [...] background or padding
area of the element" has been corrected to
<blockquote><p>Even if the image is fixed, it is still only visible
when it is in the background, padding <ins>or border</ins> area of the
element.</blockquote>
<!--
<h3 id="x73"><a href="fonts.html#font-family-prop">Section 15.2.2 Font family</a></h3>
<p>Replaced the sentence that
said: "Although many fonts provide the "missing character" glyph,
typically an open box, as its name implies this should not be
considered a match except for the last font in a font set" by:
<blockquote>
<p>Although many fonts provide the "missing character" glyph,
typically an open box, as its name implies this should not be
considered a match.
</blockquote>
-->
<!--
<h3 id="x74"><a href="fonts.html#font-properties">Section 15.2.4</a></h3>
<p>Added to the explanation of 'font-size' the following
clarification: "The font size corresponds to the em square,
a concept used in typography.
Note that certain glyphs may bleed outside their em squares."</p>
-->
<!--
<h3 id="x75"><a href="fonts.html#algorithm">Section 15.5 Font matching
algorithm</a></h3>
<p>In point 8, replaced the
sentence that says: "If a particular character cannot be displayed
using this font, the UA should indicate that a character is not being
displayed (for example, using the 'missing character' glyph)" by
<blockquote>
<p>If a particular character cannot be displayed using this font,
then the UA has no suitable font for that character. The UA should
map each character for which it has no suitable font to a visible
symbol chosen by the UA, preferably a "missing character" glyph
from one of the font faces available to the UA.
</blockquote>
-->
<h3 id="x76"><a href="text.html#indentation-prop">Section 16.1</a></h3>
<p>Added to:</p>
<blockquote>
<p>
The value of 'text-indent' may be negative, but there may be
implementation-specific limits.
</p>
</blockquote>
<p>the following clarification: "If the value of 'text-indent'
is negative, the value of 'overflow' will affect whether the
text is visible."
<h3 id="x77"><a href="text.html#alignment-prop">16.2 Alignment: the 'text-align' property</a></h3>
<p>Changed "double justify" to "justify" under "left, right, center,
and justify".
<h3 id="x78"><a href="tables.html#table-layers">Section 17.5.1 Table layers and
transparency</a></h3>
<p>In point 6, changed 'These
"empty" cells are transparent' to:
<blockquote>
<p>If the value of their 'empty-cells' property is 'hide'
these "empty" cells are transparent through the cell, row, row group,
column, and column group backgrounds, letting the table background
show through.</blockquote>
<p>To remove ambiguity about the position of backgrounds on rows and
column, the following paragraph was added after point 6:
<blockquote><p>the edges of the rows, columns, row groups and column
groups in the <a href="#collapsing-borders">collapsing borders
model</a> coincide with the hypothetical grid lines on which the
borders of the cells are centered. (And thus, in this model, the rows
together exactly cover the table, leaving no gaps; ditto for the
columns.) In the <a href="#separated-borders">separated borders
model,</a> the edges coincide with the <a
href="box.html#border-edge">border edges</a> of cells. (And thus, in
this model, there may be gaps between the rows and columns,
corresponding to the <span
class="propinst-border-spacing">'border-spacing'</span>
property.)</blockquote>
<p>At the end of the section
added the following paragraph:
<blockquote><p>Note that if the table has 'border-collapse: separate',
the background of the area given by the 'border-spacing' property is
always the background of the table element. See 17.6.1</blockquote>
<h3 id="table-width"><a href="tables.html#width-layout">Section 17.5.2 Table width algorithms</a></h3>
<p>Added the following paragraph after the initial paragraph of this
section:
<blockquote>
<p>Note that this section overrides the rules that apply to
calculating widths as described in <a
href="visudet.html#Computing_widths_and_margins">section 10.3</a>. In
particular, if the margins of a table are set to '0' and the width to
'auto', the table will not automatically size to fill its containing
block. However, once the calculated value of 'width' for the table is
found (using the algorithms given below or, when appropriate, some
other UA dependant algorithm) then the other parts of section 10.3
do apply. Therefore a table can be centered using left and right
'auto' margins, for instance.
</blockquote>
<p>The WG may introduce ways of automatically making tables fit their
containing blocks in CSS3.
<h3 id="s-17-6-1"><a href="tables.html#separated-borders">17.6.1 The separated borders model</a></h3>
<p>Added clarification about alignment of row/column backgrounds. The
sentence "This space is filled with the background of the table
element" was replaced by:
<blockquote>In this space, the row, column, row group, and column
group backgrounds are invisible, allowing the table background to show
through.</blockquote>
<h3 id="x79"><a href="tables.html#empty-cells">Borders around empty cells: the
'empty-cells' property</a></h3>
<p>The 'empty-cells' property
not only controls the borders, but also the background.
<h3 id="x80"><a href="tables.html#collapsing-borders">Section 17.6.2 The
collapsing borders model</a></h3>
<p>In the sentence after the question, added "and
padding-left<sub>i</sub> and padding-right<sub>i</sub> refer
to the left (resp., right) padding of cell i."
<h3 id="x81"><a href="ui.html#system-colors">Section 18.2</a></h3>
<p>For the 'ButtonHighlight' value, changed the description
from "Dark shadow" to "Highlight color".
<h3 id="x82"><a href="aural.html#speaking-props">Section A.3</a></h3>
<p>The parenthetical phrase "somewhat analogous to the 'display' property"
was misleading. The 'speak' property resembles 'visibility' in
some ways and 'display' in others.
<h3 id="x84"><a href="grammar.html#q2">Appendix G.2 Lexical scanner</a></h3>
<p>Removed the following line from the scanner as it
does not appear in the grammar:</p>
<pre>
"@"{ident} {return ATKEYWORD;}
</pre>
<p>The DIMEN token is in the scanner to ensure that a number followed