-
Notifications
You must be signed in to change notification settings - Fork 790
Expand file tree
/
Copy pathissues-4.html
More file actions
1247 lines (1093 loc) · 40.6 KB
/
issues-4.html
File metadata and controls
1247 lines (1093 loc) · 40.6 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.01//EN">
<title>CSS2.1 Issues List</title>
<style type="text/css">
@import "http://www.w3.org/StyleSheets/TR/base.css";
dd { margin: 1em 2em; padding-left: 0; }
dd pre { margin: 0; }
table a:link, table a:visited {color: inherit; text-decoration: underline}
th:first-child, td:first-child {text-align: right}
table {border-collapse: collapse; margin: 1.2em 2em}
th, td {padding: 0em 0.4em}
.m {color: #C90}
.o {color: #900}
dfn {font-style: italic}
</style>
<h1>CSS2.1 Issues List</h1>
<!-- beginning of DoC -->
<p>Disposition of comments for the WD of 6 November
2006 of <a
href="http://www.w3.org/TR/2006/WD-CSS21-20061106/">Cascading Style
Sheets, level 2 revision 1</a> as of April 26, 2007.
<h2>Summary of public comments</h2>
<table>
<thead>
<tr><th>Issue <th>Response
<tbody>
<tr><td><a href="#issue-2">2</a> <td class=n>no response
<tr><td><a href="#issue-3">3</a> <td class=a><a
href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007AprJun/0156.html">
accept</a>
<tr><td><a href="#issue-4">4</a> <td class=n>no response
<tr><td><a href="#issue-5">5</a> <td class=n>no response
<tr><td><a href="#issue-6">6</a> <td class=n>no response
<tr><td><a href="#issue-7">7</a> <td class=n>no response
<tr><td><a href="#issue-8">8</a> <td class=n>no response
<tr><td><a href="#issue-11">11</a> <td class=n>no response
<tr><td><a href="#issue-12">12</a> <td class=m><a
href="http://lists.w3.org/Archives/Public/www-style/2007Apr/0070.html">
maybe</a>
<tr><td><a href="#issue-13">13</a> <td class=n>no response
<tr><td><a href="#issue-16">16</a> <td class=n>no response
<tr><td><a href="#issue-17">17</a> <td class=n>no response
<tr><td><a href="#issue-19">19</a> <td class=n>no response
<tr><td><a href="#issue-25">25</a> <td class=n>no response
<tr><td><a href="#issue-29">29</a> <td class=n>no response
<tr><td><a href="#issue-31">31</a> <td class=a><a
href="http://lists.w3.org/Archives/Public/www-style/2007Apr/0197.html">
accept</a>
<tr><td><a href="#issue-32">32</a> <td class=n>no response
</table>
<p>(Other issues were either editorial or were internal to the WG.)
<p><dfn>no response</dfn> = no response from commenter since
announcing the WG's resolution; <dfn>maybe</dfn> = commenter wants
more info before deciding; <dfn>objection</dfn> = commenter disagrees
with the resolution; <dfn>accept</dfn> = commenter agrees with
resolution.
<!-- end of DoC -->
<h2 id="issue-1">Issue 1</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2006Nov/0020.html">http://lists.w3.org/Archives/Public/www-style/2006Nov/0020.html</a></dd>
<dt>Description</dt>
<dd><pre>
"A declaration block (also called a declaration block in the following
text)..."
Remove "(also called a declaration block in the following text)" completely.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Assumed editorial.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-2">Issue 2</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2006Nov/0006.html">http://lists.w3.org/Archives/Public/www-style/2006Nov/0006.html</a></dd>
<dt>Description</dt>
<dd><pre>
Behavior of blocks that establish a new block formatting context
in the presence of floats.
</pre></dd>
<dt>Proposal</dt>
<dd><pre>
<a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0303.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0303.html</a>
1. Link the words "may become narrower" in 9.4.1 to the 5th
paragraph of 9.5 "Floats"
2. In the first sentence of of that 5th paragraph of 9.5,
change "margin box" to "border box" (Issue 21).
3. Add this sentence at the end of that 5th paragraph of 9.5:
"They may even make the border box of said element narrower
than defined by section 10.3.3. CSS2 does not define when a
UA may put said element next to the float or by how much
said element may become narrower."
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Proposal accepted.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-3">Issue 3</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2006Sep/0065.html">http://lists.w3.org/Archives/Public/www-style/2006Sep/0065.html</a></dd>
<dt>Description</dt>
<dd><pre>
Why aren't overlapping table cells required?
</pre></dd>
<dt>Proposal</dt>
<dd><pre>
<a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0303.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0303.html</a>
Leave spec as-is.
New proposal:
<a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007AprJun/0250.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007AprJun/0250.html</a>
Add explicitly undefined cases to bullet 5 in 17.5
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
(After discussing with the Director:) the layout of illegal XHTML
tables (and all similar combinations of rowspan/colspan in other
formats) when rendered with CSS's table properties is explicitly
undefined, as follows:
Change this text in bullet 5 of 17.5
The rectangle must be as far to the left as possible, but it
may not overlap with any other cell box, and must be to the
right of all cells in the same row that are earlier in the
source document. (This constraint holds if the 'direction'
property of the table is 'ltr'; if the 'direction' is 'rtl',
interchange "left" and "right" in the previous sentence.)
to
The rectangle must be as far to the left as possible, but the
part of the cell in the first column it occupies must not
overlap with any other cell box (i.e., a row-spanning cell
starting in a prior row), and the cell must be to the right of
all cells in the same row that are earlier in the source
document. If this position would cause a column-spanning cell
to overlap a row-spanning cell from a prior row, CSS does not
define the results: implementations may either overlap the
cells (as is done in many HTML implementations) or may shift
the later cell to the right to avoid such overlap. (This
constraint holds if the 'direction' property of the table is
'ltr'; if the 'direction' is 'rtl', interchange "left" and
"right" in the previous two sentences.)
Also change the following example and its image caption
correspondingly.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-4">Issue 4</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://fantasai.inkedblade.net/style/specs/css2.1/min-max-replaced-2">http://fantasai.inkedblade.net/style/specs/css2.1/min-max-replaced-2</a></dd>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2006Nov/0034.html">http://lists.w3.org/Archives/Public/www-style/2006Nov/0034.html</a></dd>
<dt>Description</dt>
<dd><pre>
The Min-Max Issue
</pre></dd>
<dt>Proposal</dt>
<dd><pre>
Leave spec as-is and continue with image-scaling in CSS3. Add note:
Note: In cases where an explicit width or height is set and the other
dimension is auto, applying a minimum or maximum constraint on the
auto side can cause an over-constrained situation. The spec is clear
in the behavior but it might not be what the author expects. The CSS3
image-fit property can be used to obtain different results in this
situation.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
No normative change, add warning note to authors.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-5">Issue 5</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2006Nov/0049.html">http://lists.w3.org/Archives/Public/www-style/2006Nov/0049.html</a></dd>
<dt>URI</dt>
<dd><a href="http://www.w3.org/Style/CSS/Test/CSS2.1/current/t1202-counters-17-d.htm">http://www.w3.org/Style/CSS/Test/CSS2.1/current/t1202-counters-17-d.htm</a></dd>
<dt>Description</dt>
<dd><pre>
Test assumes
:before, :after { white-space: pre-line }
is not there, even though it's in the sample style sheet.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Repeat "white-space: pre" on :before, :after in test t1202-counters-17-d.htm
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-6">Issue 6</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2006Dec/0021.html">http://lists.w3.org/Archives/Public/www-style/2006Dec/0021.html</a></dd>
<dt>Description</dt>
<dd><pre>
issues-3.103: Add reference to Unicode Standard, not just ISO10646.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
We already reference Unicode.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-7">Issue 7</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2006Dec/0021.html">http://lists.w3.org/Archives/Public/www-style/2006Dec/0021.html</a></dd>
<dt>Description</dt>
<dd><pre>
issues-3.104: Clarify that CSS reserving all property values and
@keywords does not retroactively make invalid SVG 1.0/1.1 documents
with external stylesheets.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
We already agreed to publish an CSS3 SVG module.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-8">Issue 8</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2006Dec/0021.html">http://lists.w3.org/Archives/Public/www-style/2006Dec/0021.html</a></dd>
<dd><a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0117.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0117.html</a></dd>
<dt>Description</dt>
<dd><pre>
issues-3.105: RGB colors may be clipped prematurely.
<a href="http://www.w3.org/Style/Group/css2-src/syndata.html">http://www.w3.org/Style/Group/css2-src/syndata.html</a>#color-units
</pre></dd>
<dt>Proposal</dt>
<dd><pre>
(From Bert and Melinda)
1. Replace note after last example in 4.3.6 with
"Note. Mapping or clipping of color values should be done to
the actual device gamut if known (which may be larger or
smaller than 0..255)."
2. In the paragraph before that example, change
"Values outside the device gamut should be clipped"
to
"Values outside the device gamut should be clipped or
mapped into the gamut when the gamut is known."
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Proposal accepted.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-9">Issue 9</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2006Dec/0021.html">http://lists.w3.org/Archives/Public/www-style/2006Dec/0021.html</a></dd>
<dt>Description</dt>
<dd><pre>
issues-3.106: Make reference to CSS3 obviously non-normative.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Assumed editorial. Changed "Implementors should look at CSS3 Lists"
to "Implementors are advised to look at CSS3 Lists" in the section
"Features at risk" on the cover page.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-10">Issue 10</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2006Dec/0038.html">http://lists.w3.org/Archives/Public/www-style/2006Dec/0038.html</a></dd>
<dt>Description</dt>
<dd><pre>
Poster has a question about floats in absolutely-positioned elements,
apparently can't find answer in spec. If we can't find it either, this
is an issue. Otherwise, we just need to post a reply with the answer
and add his test cases to the test suite.
</pre></dd>
<dt>Reply</dt>
<dd><pre><a href="http://lists.w3.org/Archives/Public/www-style/2007Feb/0104.html">http://lists.w3.org/Archives/Public/www-style/2007Feb/0104.html</a>
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
No change.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<
8096
/div>
<h2 id="issue-11">Issue 11</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2006Dec/0057.html">http://lists.w3.org/Archives/Public/www-style/2006Dec/0057.html</a></dd>
<dt>Description</dt>
<dd><pre>
Empty inline elements should act like display: none; (?)
[Needs testcase]
</pre></dd>
<dt>Proposal 1</dt>
<dd><pre>
Line boxes that contain no text, no spaces, and no in-flow content
(such as images, inline blocks or inline tables), and don't end with
a line feed must be taken out of flow and not rendered. Inline
elements on such line boxes must not be rendered. For the purposes
of finding the static position for positioning or position for
floats, an anonymous block that acts as a parent of these elements
must be assumed to replace the line box.
</pre></dd>
<dt>Proposal 2</dt>
<dd><pre>
Line boxes that contain no text, no preserved white space, and no
in-flow content (such as images, inline blocks or inline tables),
and don't end with a line feed must be taken out of flow and not
rendered. Inline elements on such line boxes must not be rendered.
The static position and the position for floats is calculated as
if such inline elements were anonymous blocks.
</pre></dd>
<dt>Proposal 3</dt>
<dd><pre>
Line boxes that contain no text, no preserved white space, no inline
elements with non-zero margins, padding, or borders, and no other
in-flow content (such as images, inline blocks or inline tables),
and don't end with a line feed must be taken out of flow and not
rendered. Inline elements on such line boxes must not be rendered.
The static position of such inline elements is calculated with
respect to an anonymous block that replaces the line box. This
anonymous block is the containing block for any descendant floats.
</pre></dd>
<dt>Proposal 4</dt>
<dd><pre>
Line boxes that contain no text, no preserved white space, no inline
elements with non-zero margins, padding, or borders, and no other
in-flow content (such as images, inline blocks or inline tables),
and don't end with a line feed must be taken out of flow and not
rendered. Inline elements on such line boxes must not be rendered.
The static and relatively-positioned position of such inline elements
is the static position of an anonymous block that replaces the
line box. This anonymous block is the containing block for any
descendant floats.
</pre></dd>
<dt>Proposal 5</dt>
<dd><pre>
Empty inline elements without padding, margins or borders (and ignored
height) on an otherwise empty line box do not participate in rendering.
For positioning purposes treat the empty inline as an empty block box.
</pre></dd>
<dt>Proposal 6</dt>
<dd><pre>
Line boxes that contain no text, no preserved white space, no inline
elements with non-zero margins, padding, or borders, and no other
in-flow content (such as images, inline blocks or inline tables),
and don't end with a line feed must be treated as zero-height line
boxes. For the purposes of margin collapsing, this line box must be
ignored.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Proposal 6 accepted for 9.4.2.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-12">Issue 12</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2006Dec/0086.html">http://lists.w3.org/Archives/Public/www-style/2006Dec/0086.html</a></dd>
<dd><a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0117.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0117.html</a></dd>
<dt>Description</dt>
<dd><pre>
Dissent on change to ignoring broken URIs in 'content'.
</pre></dd>
<dt>Proposal</dt>
<dd><pre>
Reply: <a href="http://lists.w3.org/Archives/Public/www-style/2007Feb/0106.html">http://lists.w3.org/Archives/Public/www-style/2007Feb/0106.html</a>
No change.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
No change.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-13">Issue 13</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2007Jan/0001.html">http://lists.w3.org/Archives/Public/www-style/2007Jan/0001.html</a></dd>
<dt>Description</dt>
<dd><pre>
Definition of replaced element unclear about embedded <svg> elements,
uses undefined term "CSS formatter".
</pre></dd>
<dt>Proposal</dt>
<dd><pre>
Change "CSS formatter" to "CSS formatting model" and either
a) Remove "The rendered content of a replaced element comes
from outside the source document" or
b) Replace it with "The rendered content of a replaced element
is outside the scope of this specification"
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Proposal accepted with wordsmithed option b:
"How a replaced element's content is rendered is not defined by
this specification."
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-14">Issue 14</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2006OctDec/0183.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2006OctDec/0183.html</a></dd>
<dt>Description</dt>
<dd><pre>
The third bullet in Section 3.2 says that UA's that render must respect
points 1-5. Should this be point 1-6?
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Assumed editorial.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-16">Issue 16</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2007Jan/0040.html">http://lists.w3.org/Archives/Public/www-style/2007Jan/0040.html</a></dd>
<dt>Description</dt>
<dd><pre>
Unclear whether escapes are allowed in !important tokens.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Assumed editorial. Fixed Appendix G to allow escapes.
Reply to www-style/Bjoern:
<a href="http://lists.w3.org/Archives/Public/www-style/2007Feb/0048.html">http://lists.w3.org/Archives/Public/www-style/2007Feb/0048.html</a>
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-17">Issue 17</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2007Jan/0041.html">http://lists.w3.org/Archives/Public/www-style/2007Jan/0041.html</a></dd>
<dt>Description</dt>
<dd><pre>
Define whether -0 is a non-negative number. (Browsers seem to treat
it as non-negative.)
</pre></dd>
<dt>Proposal</dt>
<dd><pre>
Add "-0 is equivalent to 0 and is not a negative number."
to the end of the first paragraph in 4.3.1.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Proposal accepted.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-18">Issue 18</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2007Jan/0042.html">http://lists.w3.org/Archives/Public/www-style/2007Jan/0042.html</a></dd>
<dt>Description</dt>
<dd><pre>
Replace <list-style-type> with <'list-style-type'> in syndata and generate
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Assumed editorial.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-19">Issue 19</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2007Jan/0062.html">http://lists.w3.org/Archives/Public/www-style/2007Jan/0062.html</a></dd>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2007Jan/0064.html">http://lists.w3.org/Archives/Public/www-style/2007Jan/0064.html</a></dd>
<dt>Description</dt>
<dd><pre>
What to do with Unicode escapes above U+10FFFF
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
A UA should display something, such as a replacement character or a
missing glyph character. Bert to add something to either chapter 4
or chapter 15.
Actual text added to 4.1.3:
If the number is outside the range allowed by Unicode (e.g.,
"\110000" is above the maximum 10FFFF allowed in current Unicode),
the UA may replace the escape with the "replacement character"
(U+FFFD). If the character is to be displayed, the UA should show a
visible symbol, such as a "missing character" glyph (cf. 15.2, point
5).
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-20">Issue 20</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2007Jan/0070.html">http://lists.w3.org/Archives/Public/www-style/2007Jan/0070.html</a></dd>
<dt>Description</dt>
<dd><pre>
Changes section out-of-sync.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Assumed editorial.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-21">Issue 21</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0088.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0088.html</a></dd>
<dt>Description</dt>
<dd><pre>
Should floats be excluded from the margin box or the border box of
elements flowing alongside?
</pre></dd>
<dt>Proposal</dt>
<dd><pre>
Change "The margin box of a table..." to "The border box of a table..."
in the 5th paragraph of 9.5.
Group is leaning towards accepting this proposal, waiting for feedback
from HP (and others who want to think about it) before making it final.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Proposal accepted.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-22">Issue 22</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0170.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0170.html</a></dd>
<dt>Description</dt>
<dd><pre>
"Note. After a certain amount of time, user agents may choose to
return a visited link to the (unvisited) ':link' state." should be
normative.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Replace the note in 5.11.2 by this (normative) paragraph:
UAs may return a visited link to the (unvisited) ':link' state at
some point.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-23">Issue 23</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0168.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0168.html</a></dd>
<dt>Description</dt>
<dd><pre>
Clearly specify handling of unicameral scripts.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
In 16.5, replace
Conforming user agents may consider the value of 'text-transform'
to be 'none' for writing scripts for which there is no transform.
by
Only characters belonging to bicameral scripts [xyz] are
affected.
and add a bibliographic reference [xyz] to
<a href="http://www.unicode.org/reports/tr21/tr21-5.html">http://www.unicode.org/reports/tr21/tr21-5.html</a>#Introduction
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-24">Issue 24</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0209.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0209.html</a></dd>
<dd><a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2006JulSep/0217">http://lists.w3.org/Archives/Member/w3c-css-wg/2006JulSep/0217</a></dd>
<dt>Description</dt>
<dd><pre>
We decided a change to the priority rules among possible page
breaks, but no action was assigned at the time. So here is the
action:
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
In section 13.3.3, change
If the above doesn't provide enough break points to keep content
from overflowing the page boxes, then rules B and D are dropped in
order to find additional breakpoints.
If that still does not lead to sufficient break points, rules A
and C are dropped as well, to find still more break points.
to
If the above doesn't provide enough break points to keep content
from overflowing the page boxes, then rules A, B and D are dropped in
order to find additional breakpoints.
If that still does not lead to sufficient break points, rule
C is dropped as well, to find still more break points.
(I.e., 'A' should be added to the first paragraph and deleted from
the last paragraph.)
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-25">Issue 25</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2007Jan/0098.html">http://lists.w3.org/Archives/Public/www-style/2007Jan/0098.html</a></dd>
<dt>Description</dt>
<dd><pre>
Define what happens to margin/border/padding/text-decoration where
element is broken.
</pre></dd>
<dt>Proposal</dt>
<dd><pre>
(From Bert, modified by Melinda:)
<a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0303.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0303.html</a>
Add to the end of 13.3.1:
"When a page break splits a box, the box's margins, borders, and
padding have no visual effect where the split occurs."
or:
"When a box is interrupted at the bottom of one page and continued
on the top of the next, the box's margins, borders, and padding
are not rendered at the bottom and top of the respective pages.
Future specifications may define properties to modify this
behavior. (At the time of writing, a property 'border-break'
[CSS3BG] is under consideration.)"
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
First proposal accepted.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-26">Issue 26</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0069.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0069.html</a></dd>
<dt>Description</dt>
<dd><pre>
This is a request from SVG.
Intrinsic ratio is ignored when there is neither intrinsic height or
width. Should use available width like for non-replaced blocks where
possible and calculate height from ratio.
Example (use FF or Opera):
SVG image with intrinsic ratio, but no intrinsic size:
<a href="http://fantasai.inkedblade.net/style/tests/issues/intrinsic-ratio.svg">http://fantasai.inkedblade.net/style/tests/issues/intrinsic-ratio.svg</a>
Document with a wide body that includes this image:
<a href="http://fantasai.inkedblade.net/style/tests/issues/intrinsic-ratio-1">http://fantasai.inkedblade.net/style/tests/issues/intrinsic-ratio-1</a>
</pre></dd>
<dt>Proposals</dt>
<dd><pre>
1. Use 300px by 150px. This will help us exit CR, because it's what
implementations do today. It is not what CDF agreed to, and it's
not what CDF or SVG wants.
Text: current text
2. Use available width and intrinsic ratio where possible (fall back
to 300px otherwise). This is not what implementations do today.
It is what SVG wants, what CDF expected the spec to say, and it
is the most useful for authoring.
Text: <a href="http://lists.w3.org/Archives/Member/w3c-svg-wg/2006OctDec/0373.html">http://lists.w3.org/Archives/Member/w3c-svg-wg/2006OctDec/0373.html</a>
(+ changes for #3 to handle fallback)
3. Use 300px times intrinsic ratio. This is not what implementations
do today, and it's not what CDF or SVG wants.
Text: Remove "'width' has some other computed value," from the 3rd
paragraph in 10.6.2.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Proposal 2 accepted.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-27">Issue 27</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0121.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0121.html</a></dd>
<dt>Description</dt>
<dd><pre>
In 8.3.1
"An element's own margins are adjoining if ... it has neither vertical
borders nor vertical padding"
Term "vertical borders" and "vertical padding" is confusing.
</pre></dd>
<dt>Proposal</dt>
<dd><pre>
Replace "vertical" with "top or bottom".
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Assumed editorial.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-28">Issue 28</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://www.w3.org/TR/css3-speech/">http://www.w3.org/TR/css3-speech/</a>#aural-model</dd>
<dt>Description</dt>
<dd><pre>
The informative appendix on aural properties
<a href="http://www.w3.org/Style/Group/css2-src/aural.html">http://www.w3.org/Style/Group/css2-src/aural.html</a>#pause-props
says
# These properties specify a pause to be observed before (or after)
# speaking an element's content. Values have the following meanings:
# ...
# The pause is inserted between the element's content and any
# 'cue-before' or 'cue-after' content.
To be consistent with CSS3 Speech, we can replace
"an element's content"
with
"an element's cues and content"
and delete the other sentence.
Otherwise, we should add a note after that last sentence.
Note: In CSS3 pauses are inserted around the cues and
content rather than between them. See [CSS3 Speech] for
details.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Add note.
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-29">Issue 29</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2007Mar/0004.html">http://lists.w3.org/Archives/Public/www-style/2007Mar/0004.html</a></dd>
<dt>Description</dt>
<dd><pre>
Spec is not clear on whether 'clip'-ed content that would have overflowed
should be considered as causing overflow.
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Add "Content that has been clipped does not cause overflow" to after
"... outside the clipping region" in section 11.1.2
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-30">Issue 30</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/att-0376/MarginCollapsingSamples070302.htm">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/att-0376/MarginCollapsingSamples070302.htm</a></dd>
<dt>Description</dt>
<dd><pre>
9.5.2 defines behavior of 'clear' as follows:
Computing the clearance of an element on which 'clear' is set is done
by first determining the hypothetical position of the element's top
border edge within its parent block. This position is determined after
the top margin of the element has been *collapsed* with previous
adjacent margins (including the top margin of the parent block).
If the element's top border edge has not passed the relevant floats,
then its clearance is set to the amount necessary to place the border
edge of the block even with the bottom outer edge of the lowest float
that must be cleared.
However 8.3.1 describes collapsing margins as
In this specification, the expression collapsing margins means that
adjoining margins (no non-empty content, padding or border areas or
*clearance* separate them) of two or more boxes (which may be next to
one another or nested) combine to form a single margin.
This creates a circular reference which makes the two rules contradictory.
</pre></dd>
<dt>Original proposal from MS</dt>
<dd><pre>
In 8.3.1, remove all 5 instances of the word 'clearance' (and whole sentences
that are not needed without 'clearance')
Note:
Clearance was added as a concept at Oslo f2f in 2003. It was added both
to 9.5.2 and 8.3.1. However since margin collapsing happens before
clearance, it doesn't need to have clearance-related rules.
</pre></dd>
<dt>Alternate proposal from Hyatt</dt>
<dd><pre><a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0512.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0512.html</a>
</pre></dd>
<dt>Alternate proposal from Ian</dt>
<dd><pre><a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0535.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0535.html</a>
</pre></dd>
<dt>Alternate proposal from Ian/Elika:</dt>
<dd><pre>
<a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0538.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0538.html</a>
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
Ian's text accepted:
<a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0535.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0535.html</a>
</pre></dd>
<dt>Status</dt>
<dd><p>Issue closed.</p></dd>
</dl>
<h2 id="issue-31">Issue 31</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2007Mar/0035.html">http://lists.w3.org/Archives/Public/www-style/2007Mar/0035.html</a></dd>
<dt>Description</dt>
<dd><pre>
Make XHTML <body> magic like HTML <body>.
</pre></dd>
<dt>Proposal</dt>
<dd><pre>
6.4.4 paragraph 2: change "For HTML" to "For HTML and XHTML".
11.1.1: Change the sentence "HTML UAs must instead apply the 'overflow'
property from the BODY element to the viewport, if the value on the
HTML element is 'visible'." to:
When the root element is an HTML "HTML" element or an XHTML "html"
element, and that element has an HTML "BODY" element or an XHTML
"body" element as a child, user agents must instead apply the
'overflow' property from the first such child element to the
viewport, if the value on the root element is 'visible'.
14.2 paragraph 4: change to:
For HTML documents, however, we recommend that authors specify the
background for the BODY element rather than the HTML element. For
documents whose root element is an HTML "HTML" element or an XHTML
"html" element that has computed values of 'transparent'
for 'background-color' and 'none' for 'background-image', user
agents must instead use the computed value of those properties from
that element's first HTML "BODY" element or XHTML "body" element
child when painting backgrounds for the canvas, and must not paint a
background for that child element. Such backgrounds must also be
anchored at the same point as they would be if they were painted
only for the root element.
17.5 paragraph 2: change the last sentence to: "These rules do not
apply to HTML or XHTML; HTML imposes its own limitations on row and
column spans."
17.5 final example: This would need various editorial changes to
indicate that the second example is not XHTML but some non-HTML XML
vocabulary.
</pre></dd>
<dt>Alternate proposal from Ian/Elika:</dt>
<dd><pre>
<a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0538.html">http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0538.html</a>
</pre></dd>
<dt>Resolution</dt>
<dd><pre>
No change at this point.
</pre></dd>
<dt>Resolution 2</dt>
<dd><pre>
Mark this behavior at risk.
</pre></dd>
<dt>Status</dt>
<dd>Issue closed.</dd>
</dl>
<h2 id="issue-32">Issue 32</h2>
<dl>
<dt>URI</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/2007Mar/0068">http://lists.w3.org/Archives/Public/www-style/2007Mar/0068</a></dd>
<dt>Description</dt>
<dd><pre>
page-break-inside on child can override parent, but the same isn't