forked from w3c/csswg-drafts
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy patherrata.src
More file actions
927 lines (685 loc) · 31.9 KB
/
errata.src
File metadata and controls
927 lines (685 loc) · 31.9 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Errata in _THE_ID_</title>
<!-- Changed by: Ian B. Jacobs, 28-Sep-1998 -->
<LINK rel="start" href="http://www.w3.org/TR/REC-css2">
<style type="text/css">
body {
background: white;
color: black;
}
</style>
<base href="_THIS_VERSION_/">
</head>
<body>
<p align="right"><a href="http://www.w3.org/"><img
src="http://www.w3.org/Icons/w3c_home.gif" alt="W3C" align="left" border="0"
hspace="0"></a><br clear="all"></p>
<H1 align="center">Errata in _THE_ID_</H1>
<dl>
<dt>This document:
<dd><a href="_THE_UPDATE_DIR_/_THE_ID_-errata.html">
_THE_UPDATE_DIR_/_THE_ID_-errata.html</a>
<dt>Last revised:
<dd>$Date: 2000-08-08 18:36:04 $
</dl>
<dl>
<dt>This document records known errors in the document:
<dd><a href="_THIS_VERSION_">_THIS_VERSION_</a>
<dt>The latest version of the CSS 2 specification:
<dd><a href="_THE_LATEST_VERSION_">_THE_LATEST_VERSION_</a>
</dl>
<HR>
<P>Please email error reports to <a
href="mailto:css2-editors@w3.org">css2-editors@w3.org</a>.
<h2><a name="known-errors">Known Errors</a></h2>
<H3>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
do not enforce this rule: 'border-top', 'border-right',
'border-bottom', 'border-left', 'border', 'background', 'font',
'list-style', 'cue', and 'outline'.
<H3><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') should say that
they don't apply to table rows, row groups, header groups, footer
groups, columns, and column groups.
<P>For a row group
<H3><a href="syndata.html#tokenization">Section 4.1.1</a> (and
<a href="grammar.html#q2">D2</a>)</H3>
<UL>
<LI>The "nmchar" token should also allow the range "A-Z".
<LI>In the rule for "any" (in the core syntax), change "FUNCTION"
to "FUNCTION any* ')'".
</UL>
<H3><a href="syndata.html#q4">4.1.3 Characters and case</a></H3>
<P>In the third bullet, add 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."
<H3><a href="syndata.html#values">Section 4.3 (Double sign problem)</a></H3>
<P>Several values described in subsections of this section
incorrectly allow two "+" or "-" signs at their beginnings.
<a href="syndata.html#length-units">Lengths</a>, for instance,
are described as follows:</P>
<BLOCKQUOTE>
The format of a length value (denoted by <length> in this
specification) is an optional sign character ('+' or '-', with '+'
being the default) immediately followed by a <number>
(with or without a decimal point)
immediately followed by a unit identifier (e.g., px, deg, etc.).
</BLOCKQUOTE>
<P>However, since <number> already allows a "+" or "-"
sign, the above definition means two signs may appear. The following
value types allow two signs but are meant to allow one
initial sign only:</P>
<UL>
<LI><a href="syndata.html#length-units">Lengths</a>
<LI><a href="syndata.html#percentage-units">Percentages</a>
<LI><a href="syndata.html#angle-units">Angles</a>
</UL>
<H3><a href="syndata.html#color-units">Section 4.3.6</a></H3>
<P>Delete the comments about range
restriction after the following examples:
<PRE>
EM { color: rgb(255,0,0) }
EM { color: rgb(100%, 0%, 0%) }
</PRE>
<H3><a href="selector.html#q2">5.10 Pseudo-elements and pseudo-classes</a></H3>
<P>In the second bullet, the following sentence is 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><a href="box.html#mpb-examples">8.2 Example of margins, padding, and borders</a></H3>
<P>The colors in the example HTML do not match the colors in the
image.
<H3><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>Change <'border-top-width'> to <border-width> as the first
value option for 'border-top', 'border-right', 'border-bottom',
and 'border-left', and change <'border-style'> to <border-style>.
For 'border', change <'border-width'>
to <border-width> and
<'border-style'> to <border-style>.
<H3><a href="visuren.html#choose-position">Section 9.3.1</a></H3>
<P>The definition of the value 'static' should
say that the properties 'top', 'right', 'bottom', and 'left'
do not apply.
<h3><a href="visuren.html#position-props">Section 9.3.2</a></H3>
<P>The properties 'top', 'right', 'bottom', and 'left', incorrectly
refer to offsets with respect to a box's content edge. The proper edge
is the margin edge. Thus, for 'top', the description should read,
"This property specifies how far a box's top margin edge is offset
below the top edge of the box's containing block."
<H3><a href="visuren.html#relative-positioning">Section 9.4.3</a></H3>
<P>In the first sentence, add to the end of
"Once a box has been laid out according to the normal flow"
the words "or floated,".
<H3><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>Change:</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><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." -- substitute 'rtl' for 'ltr'.
<H3><a href="visudet.html#q16">Section 10.6.2
Inline, replaced elements ...</a> (and 10.6.5)</H3>
<P>Change:</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><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 is not quite correct.
The height calculation should read as follows:</P>
<p>If <span class="propinst-top">'top'</span>, <span
class="propinst-bottom">'bottom'</span>, <span
class="propinst-margin-top">'margin-top'</span>, or <span
class="propinst-margin-bottom">'margin-bottom'</span> are 'auto',
their computed value is 0. If <span
class="propinst-height">'height'</span> is 'auto', the height depends
on whether the element has any block-level children and whether it has
padding or borders.
<P>If it only has inline-level children, the height is the distance
between the top of the topmost line box and the bottom of the
bottommost line box.
<P>If it has block-level children, the height is the distance between
the top border-edge of the topmost block-level child box and the
bottom border-edge of the bottommost block-level child box. However,
if the element has a non-zero top padding and/or top border, then the
content starts at the top <em>margin</em> edge of the topmost child.
Similarly, if the element has a non-zero bottom padding and/or bottom
border, then the content ends at the bottom <em>margin</em> edge of
the bottommost child.
<P>Only children in the normal flow are taken into account (i.e.,
floating boxes and absolutely positioned boxes are ignored, and
relatively positioned boxes are considered without their offset). Note
that the child box may be an <a
href="visuren.html#anonymous-block-level">anonymous box.</a>
<h3><a href="visufx.html#overflow">Section 11.1.1</a></h3>
<P>The example of a DIV element containing a BLOCKQUOTE
containing another DIV is not rendered correctly. The first
rule:
<PRE>
DIV { width : 100px; height: 100px;
border: thin solid red;
}
</PRE>
<P>Applies to both the external and internal DIV, so, for
example, the internal DIV box should be rendered
with a red border. The intention of the authors was
that the first style rule only apply to the external DIV.
This could be accomplished by making it more specific by
adding a "class" or "id" value to the markup and changing
the selectors accordingly.
<h3><a href="generate.html#content">12.2 The 'content'
property</a></H3>
<P>The 'content' property applies to 'display : marker' elements and
both :before and :after pseudo-elements.
<h3><a href="fonts.html#font-size-props">Section 15.2.4</a></h3>
<P>Under the 'font-size-adjust' property, in the formula given
for <number>, the variables y, a', and c are explained. An
explanation for the variable "a" is missing and should read:</P>
<PRE>
a = aspect value of first-choice font
</PRE>
<P>In the sentence beginning "In bicameral scripts..." change
"(font size divided by x-height)" to
"(x-height divided by font size)".
<h3><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><a href="fonts.html#algorithm">Section 15.5</a></h3>
<P>In bullet 2, change "the UA uses the 'font-family' descriptor"
to "the UA uses the 'font-family' property".
<P>In bullet 6, change "steps 3, 4 and 5" to
"steps 2, 3, 4 and 5".
<h3><a href="tables.html#q2"> 17.2 The CSS table model</a></h3>
<P>In the definition of <strong>table-header-group</strong>, change
"footer" to "header" in "Print user agents may repeat footer rows on
each page spanned by a table."
<h3><a href="tables.html#anonymous-boxes">17.2.1 Anonymous table objects </a></h3>
<P>Move the first bullet text to the prose before the list of
generation rules. The rules should then be the following:</P>
<ol>
<li>If the parent P of a 'table-cell' element T is not a 'table-row',
an object corresponding to a 'table-row' will be generated between P
and T. This object will span all consecutive 'table-cell' siblings
(in the document tree) of T.
<li>If the parent P of a 'table-row' element T is not a 'table',
'inline-table', or 'table-row-group' element, an
object corresponding to a 'table' element will be
generated between P and T. This object will span all consecutive siblings
(in the document tree) of T that require a 'table' parent:
'table-row', 'table-row-group', 'table-header-group',
'table-footer-group', 'table-column', 'table-column-group', and 'table-caption'.
<li>If the parent P of a 'table-column' element T is not a 'table',
'inline-table', or 'table-column-group' element, an
object corresponding to a 'table' element will be
generated between P and T. This object will span all consecutive siblings
(in the document tree) of T that require a 'table' parent:
'table-row', 'table-row-group', 'table-header-group',
'table-footer-group', 'table-column', 'table-column-group', and 'table-caption'.
<li>If the parent P of a 'table-row-group' (or 'table-header-group',
'table-footer-group', or 'table-column-group') element T is not a 'table' or 'inline-table', an
object corresponding to a 'table' element will be generated between P
and T. This object will span all consecutive siblings (in the document
tree) of T that require a 'table' parent: 'table-row',
'table-row-group', 'table-header-group', 'table-footer-group',
'table-column', 'table-column-group', and 'table-caption'.
<li>If a child T of a 'table' element (or 'inline-table') P is not a
'table-row-group', 'table-header-group', 'table-footer-group', or
'table-row' element, an object corresponding to a 'table-row' element
will be generated between P and T. This object spans all consecutive
siblings of T that are not 'table-row-group', 'table-header-group',
'table-footer-group', or 'table-row' elements.
<li>If a child T of a 'table-row-group' element (or
'table-header-group' or 'table-footer-group') P is
not a 'table-row' element, an object corresponding to a 'table-row'
element will be generated between P and T. This object spans all
consecutive siblings of T that are not 'table-row' elements.
<li>If a child T of a 'table-row' element P is not a 'table-cell'
element, an object corresponding to a 'table-cell' element will be
generated between P and T. This object spans all consecutive siblings
of T that are not 'table-cell' elements.
</ol>
<h3><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>Should be 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><a href="tables.html#q7">17.5 Visual layout of table
contents</a></h3>
<P>Change:
<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><a href="tables.html#separated-borders">Section 17.6.1 The
separated borders model</a></H3>
<P>In the image, change "cell-spacing" to "border-spacing".
<h2><a name="minor-errors">Minor Typographical Errors</a></h2>
<h3><a href="intro.html#q1">Section 2.1</a></h3>
<P>For the example with the LINK element, the list
following the example incorrectly refers to the "ref"
attribute. This should be the "href" attribute.
<h3><a href="conform.html#q1">Section 3.1</a></h3>
<P>Under the definition of "Child", the phrase
"if an only if" should read "if and only if".
<P>Under the definition of "Sibling", the last sentence should read,
"Element B is a following sibling if it comes after A in the document
tree."
<h3><a href="conform.html#text-css">Section 3.4</a></h3>
<P>The correct RFC number for the registration of the
"text/css" content type is RFC 2318, not RFC 2138.
<h3><a href="selector.html#lang">Section 5.11.4</a></h3>
<P>In "XML uses an attribute called XML:LANG", the
XML attribute should be in lowercase, i.e., xml:lang.
<h3><a href="selector.html#first-line-pseudo">Section 5.12.1</a></h3>
<P>The rendering of the first example is:</P>
<PRE>
THIS IS A SOMEWHAT LONG HTML PARAGRAPH THAT
will be broken into several lines.
</PRE>
<P>while the fictional tag sequence is given as:</P>
<PRE>
<P><B><P:first-line></B> This is a somewhat long HTML
paragraph that will <B></P:first-line></B> ...
</PRE>
<P>The word "will" should follow the fictional tag sequence
for :first-line.
<h3><a href="cascade.html#cascading-order">Section 6.4</a></h3>
<P>The last sentence in the penultimate paragraph should
begin "All user and author rules..." instead of "All rules
user and author rules...".
<h3><a href="box.html#border-color-properties">Section 8.5.2</a></h3>
<UL>
<LI>
The individual border-X-color property definitions may
also take the value 'transparent'.
<LI>The 'border-color' shorthand property should read:
<PRE>[ <color> | transparent ]{1,4} | inherit</PRE>
</UL>
<h3><a href="box.html#border-style-properties">Section 8.5.3
Border style</a></h3>
<P>Under the definition of "ridge", change "grove" to "groove".
<h3><a href="visuren.html#q5">Section 9.2.1</a></h3>
<P>In the example after the diagram, the
HTML fragment "<P>This is the content of P.</>"
should end instead with the end tag "</P>".
<h3><a href="visuren.html#anonymous">Section 9.2.2, Anonymous inline boxes</a></h3>
<P>In the (third paragraph) sentence "In the example, the color of the
anonymous initial boxes is inherited from the P, but the background is transparent", substitute the word "inline" for "initial".
<h3><a href="visuren.html#relative-positioning">Section 9.4.3</a></h3>
<P>In the second paragraph, "a new a new" should only read "a new".
<H3><a href="visuren.html#q24">Section 9.7 Relationships between 'display', 'position', and 'float'</a></H3>
<UL>
<LI>In bullet two, change "Otherwise, 'position' ..." to
"Otherwise, if 'position' ...".
<LI>In bullet four, change "remaining display properties"
to "remaining display property values".
</UL>
<h3><a href="visudet.html#q15">Section 10.6.1</a></h3>
<P>The <span class="propinst-height">'height'</span> property doesn't
apply. The height of the content area is equal to the actual font size
of the element. The vertical padding, border and margin of an inline,
non-replaced box start at the top and bottom of the font, not the
<span class="propinst-line-height">'line-height'</span>. But only the
<span class="propinst-line-height">'line-height'</span> is used to
compute the height of the line box.
<P>If more than one font size is used (this could happen when glyphs
are found in different fonts), the height of the content area is not
defined by this specification. However, we recommend that the largest
font size determine the content height.
<h3><a href="visufx.html#overflow">Section 11.1.1</a></h3>
<P>In the description of the 'scroll' value, add "a"
to "if the user agent uses [a] scrolling mechanism".</P>
<h3><a href="generate.html#content">Section 12.2</a></h3>
<P>In the definition of <counter>, the sentence "The latter
function also has two forms: 'counter(name, string)' or 'counter(name,
string, style)'" should read "two forms: 'counters(name, string)' or
'counters(name, string, style)'"
<h3><a href="generate.html#markers">Section 12.6.1</a></h3>
<P>Change the third paragraph as follows:
<BLOCKQUOTE>
<P>For the :before pseudo-element, the baseline in the marker box will
be vertically aligned with the baseline in the first line box of the
principal box. If the principal box contains no line boxes, or if
there is a block box within the principal box that is above the first
line box, the top outer edge of the marker box will be aligned with
the top outer edge of the principal box.
<P>For the :after pseudo-element, the baseline in the marker box will
be vertically aligned with the baseline in the last line box in the
principal box. If the principal box contains no line boxes, or if
there is a block box within the principal box that is below the last
line box, the bottom outer edge of the marker box will be aligned with
the bottom outer edge of the principal box.
</BLOCKQUOTE>
<h3><a href="page.html#page-box">Section 13.2</a></h3>
<P>In the following code, put a ":" after "size".
<PRE>
@page { size 8.5in 11in; margin: 2cm }
</PRE>
<h3><a href="colors.html#gamma-correction">Section 14.3</a></h3>
<P>The first sentence has one too many "the"s in
"please consult the the Gamma Tutorial...".
<h3><a href="aural.html#propdef-voice-family">Section 19.8</a></h3>
<P>In the following sentence from the
definition of the 'voice-family' property:
<BLOCKQUOTE>
If quoting is omitted, any whitespace characters before and after the
font name are ignored and any sequence of
whitespace characters inside the font name is converted to a single space.
</BLOCKQUOTE>
<P>all occurrences of the word "font" should be replaced by "voice family".
<h3><a href="grammar.html#q2">Section D.2 Lexical scanner </a></h3>
<P>Remove "RGB S*" from the rule "term" since rgb() is covered by
the "function" production, which matches counter(), atrr(), format(),
and others as well.
<h3><a href="grammar.html#tokenizer-diffs">Section D.3 Comparison of tokenization in CSS2 and CSS1 </a></h3>
<P>In the last bullet, change <code>.\55ft</code> to
<code>.\35 5ft</code>.
<h3><a href="sample.html">Appendix A: Sample Style Sheet for HTML 4.0</a></h3>
<P>The value of the 'line-height' property set for the BODY
element should be "1.12em".
<P>The OBJECT and APPLET elements should have 'display: inline'.
<h2><a name="clarifications">Clarifications</a></h2>
<h3><a href="selector.html#syndata.html#tokenization">Section 4.1.1</a></h3>
<P>DELIM should not include single or double quote. Refer also
to section 4.1.6 on strings, which must have matching single or
double quotes around them.
<h3><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 "*"' may be misleading. The note is 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><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><a href="cascade.html#cascade">6.4 The Cascade
</a></h3>
<P>Change "Rules specified in a given style sheet
override rules imported from other style sheets." to
Change "Rules specified in a given style sheet
override rules of the same weight imported from other style sheets." to
</P>
<h3><a href="box.html#box-dimensions">Section 8.1</a></h3>
<UL>
<LI>From the definition of "padding edge", delete 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. Change
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><a href="box.html#collapsing-margins">Section 8.3.1</a></h3>
<P>Add 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><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." may be
generalized. Margins, borders, and padding have no visual effect
where one or more splits occur.
<h3><a href="visuren.html#relative-positioning">Section 9.4.3</a></h3>
<P>Relatively positioned boxes do not always establish new containing
blocks. Change the second paragraph to:</P>
<BLOCKQUOTE>
<p>A relatively positioned box keeps its normal flow size, including
line breaks and the space originally reserved for it. The section on
<a href="#containing-block">containing blocks</a> explains when a
relatively positioned box establishes a new containing block.
</BLOCKQUOTE>
<P>The following attempts to clarify the meaning of the 'left',
'right', 'top' and 'bottom' properties for relative positioning:
<BLOCKQUOTE>
<P>For relatively positioned elements, 'left' and 'right' move the
box(es) horizontally, without changing their size. 'Left' moves the
boxes to the right, and 'right' moves them to the left. Since boxes
are not split or stretched as a result of 'left' or 'right', the
computed values are always: left = -right.
<P>If both 'left' and 'right' are 'auto' (their initial values), the
computed values are '0' (i.e., the boxes stay in their original
position).
<P>If 'left' is 'auto', its computed value is minus the value of 'right'
(i.e., the boxes move to the left by the value of 'right').
<P>If 'right' is specified as 'auto', its computed value is minus the
value of 'left'.
<P>If neither 'left' nor 'right' is 'auto', the position is
over-constrained, and one of them has to be ignored. If the
'direction' property is 'ltr', the value of 'left' wins and 'right'
becomes -'left'. If 'direction' is 'rtl', 'right' wins and 'left' is
ignored.
<div class="example">
<P><strong>Example.</strong>
The following two style sheets are equivalent:
<PRE>
DIV.a8 { position: relative; left: -1em; right: auto }
</PRE>
and
<PRE>
DIV.a8 { position: relative; left: auto; right: 1em }
</PRE>
</div>
<P>The 'top' and 'bottom' properties move relatively positioned
elements up or down. They also must be each other's negative. If both
are 'auto', their computed values are both '0'. If one of them is
'auto', it becomes the negative of the other. If neither is 'auto',
'bottom' is ignored (i.e., the computed value of 'bottom' will be
minus the value of 'top').
</BLOCKQUOTE>
<h3><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" means 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).
<h3><a href="visudet.html#propdef-line-height">Section 10.8.1</a></h3>
<P>Clarify 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>
<h3><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><a href="visufx.html#overflow">Section 11.1.1</a></h3>
<P>Remove '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><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> should start:</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><a href="generate.html#content">12.2 The 'content'
property</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', 'block', and 'marker'.
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><a href="generate.html#lists">Lists 12.6.2</a></h3>
<P>To clarify Hebrew numbering, add
"(Alef,
Bet, ... Tet Vav, Tet Zayin, ... Yod Tet, Kaf ...)".
<h3><a href="colors.html#q2">14.2 The background</a></h3>
<P>In the fourth paragraph, add to the end of "User agents should
observe the following precedence rules to fill in the background"
the following words: "of the canvas".
<h3><a href="fonts.html#font-properties">Section 15.2.4</a></h3>
<P>Add 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><a href="text.html#indentation-prop">Section 16.1</a></h3>
<P>Add 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><a href="text.html#alignment-prop">16.2 Alignment: the 'text-align' property</a></h3>
<P>Change "double justify" to "justify" under "left, right, center,
and justify".
<H3><a href="tables.html#collapsing-borders">Section 17.6.2 The
collapsing borders model</a></H3>
<P>In the sentence after the question, add "and
padding-left<sub>i</sub> and padding-right<sub>i</sub> refer
to the left (resp., right) padding of cell i."
<h3><a href="ui.html#system-colors">Section 18.2</a></h3>
<P>For the 'ButtonHighlight' value, change the description
from "Dark shadow" to "Highlight color".
<h3><a href="aural.html#speaking-props">Section 19.3</a></h3>
<P>The parenthetical phrase "somewhat analogous to the 'display' property"
is misleading. The 'speak' property resembles 'visibility' in
some ways and 'display' in others.
<h3><a href="sample.html">Appendix A</a></h3>
<P>The @page rule should be entirely outside the @media block:
<PRE>
@page { margin: 10% }
@media print {
H1, H2, H3,
...
}
</PRE>
<h3><a href="grammar.html#q2">Appendix D.2 Lexical scanner</a></h3>
<P>Remove the following line from the scanner as it
do 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
by an identifier is read as one token rather than two. This case
is considered an error in CSS2.
<h2><a name="changes">Changes</a></h2>
<P>The following changes are proposed by the CSS Working Group.
Please note that these changes have "working draft" status and
may not be considered definitive unless incorporated into
a revised Recommendation.
<h3><a href="visufx.html#clipping">Section 11.1.2</a></h3>
<P>While CSS2 specifies that values of "rect()" specify 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). The Working Group
proposes to revise CSS2 to conform to current practice.
<!-- <h2><a name="open-issues">Open Issues</a></h2> -->
</BODY>
</HTML>