-
Notifications
You must be signed in to change notification settings - Fork 790
Expand file tree
/
Copy pathdisposition.html
More file actions
760 lines (509 loc) · 28.6 KB
/
disposition.html
File metadata and controls
760 lines (509 loc) · 28.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
<!doctype html>
<meta charset=utf-8>
<title>Disposition of comments for Media Queries CR</title>
<style>
body { font-family: sans-serif; margin: 1em }
table {
border-collapse: collapse; margin: 1em 0; empty-cells: show;
}
th, td {
text-align: left;
vertical-align: top;
border: thin solid black;
padding: 0.2em;
}
pre {
font-size: 0.8em;
}
.proposal { background: orange }
.rejected { background:red }
.source {
background: silver;
font-size: 1.2em;
padding: 0.3em;
}
.source a { text-decoration: none }
.a { background:lightgreen }
.r { background:orange }
.fo { background:red }
</style>
<h1>Disposition of comments for Media Queries CR</h1>
<p>This document is a proposed disposition of comments on the Media Queries CR sent to the www-style mailing list. The Media Queries CR was first published <a href="http://www.w3.org/TR/2002/CR-css3-mediaqueries-20020708/">8 July 2002</a>, with an editorial revision published <a href="http://www.w3.org/TR/2007/CR-css3-mediaqueries-20070606/">6 June 2007</a>.
<p><a href="http://www.w3.org/Style/css3-updates/css3-mediaqueries-comments">Disposition of comments at last call.</a>
<p>The following color coding convention is used for comments after the 6 June 2007 publication:</p>
<ul>
<li class=a>The CSS WG agreed with the reviewer.
<li class=r>The CSS WG disagreed with the reviewer.
<li class=fo>The CSS WG disagreed with the reviewer and the reviewer raised a Formal Objection.
</ul>
<p>(There were no formal objections.)</p>
<table>
<tr><th>#<th>Comment<th>Answer
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2002Jul/0082.html">Comment</a> from Art Barstow on Tue, 16 Jul 2002; <a href="http://lists.w3.org/Archives/Public/www-style/2002Jul/0087.html">answer on www-style</a>.
<tr><td>1<td>
Given the W3C has already developed a framework (CC/PP) for
describing device capabilities (to be used by a server to
generate appropriate content), why did the CSS WG ignore this
work and develop yet another, competing solution?
<td>
Media Queries are different in several
respects. First, the communication goes the other way and the client
(rather than the server) makes the decision on what style sheet to
use. The CSS WG thinks there is room for both a client-based and a server-based
solution. Second, the work on Media Queries is continued from HTML4
where section 6.13 sketches a solution very close to Media
Queries. So, the solution was developed before the work on CC/PP
started and should not be interpreted as hostile to CC/PP.
<p>Also, see disposition of comments from Philipp Hoschka in the <a href="http://www.w3.org/Style/css3-updates/css3-mediaqueries-comments">disposition of comments to the Last Call.</a>
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2003Feb/0026">Comment</a> from Susan Lesch on Sat, 8 Feb 2003.
<tr><td>2<td>
<p>These are minor editorial comments for your Media Queries Candidate
Recommendation...
<!--
Could you move the Requirements and Related work sections to an
appendix? They're relevant but they are a little bit like a research
paper and they lead the reader in only to say that what was just
presented isn't what you are trying to specify.
In the Abstract, s/are two of media types/are two media types/
s/Status of this document/Status of This Document/
s/a web browser/a Web browser/
s/UA/user agent (UA)/ (in its first occurrence)
In the TOC and in headings (that aren't media features), words can be
capitalized in US English, for example, s/Table of contents/Table of
Contents/
s/reserved in. HTML4/reserved in HTML4./
s/Appendix (CC/PP attribute vocabulary for print and display)
describe/Appendix (CC/PP attribute vocabulary for print and display)
describes/
s/width of a the text display device/width of the text display device/
s/CamelCase/camelCase/ (normally this is a quibble but here you are
pointing out that 'charWidth' starts with lowercase)
s/Like CC/PP, RFC2534 also provides/Like CC/PP, RFC 2534 provides/
s/knowing which one of the defined media types which most closely
resembles the device./knowing which one of the defined media types most
closely resembles the device./
s/px unit/"px" unit/
s/tty devices/"tty" devices/
s/tv/"tv"/
In 5, "see CSS2, section 4.3: Values and Units" needs a link to
References for people who print this out.
s/(''(min-color: 1)/("(min-color: 1)")/
For width and height:
"viewport (as described by CSS2)" could have reference something like:
"viewport as described by CSS2 ([CSS2] section 9.1.1)."
"page box (as described by CSS2)" could be: "page box as described by
CSS2 ([CSS2] section 13.2)."
"RFC2531 [RFC2531]" needs a link and could be a normative reference.
s/greater than 300 dots per inch/greater than or equal to 300 dots per
inch/
s/pixels. in/pixels in/
The title of normative references should point to dated specs. Also,
references should have no live URI links. Here is the guideline:
http://www.w3.org/2001/06/manual/#References
Also it's unclear in [CSS2] and in [HTML401] why "Ian Jacobs" differs
from "Jacobs, I.."
In Appendix B, s/W3C working draft. (Work in progress.)/W3C Working
Draft (work in progress)./
For RFCs, s/Internet RFC/The Internet Society. RFC nnnn/
Comment on the style sheets:
- in the embedded style, where background is declared, you would also
declare color (in case someone wants to use a reversed value user
style sheet).
- in default.css, is it possible you could justify only for print?
The text looks a little choppy.
[1] http://www.w3.org/TR/2002/CR-css3-mediaqueries-20020708/
-->
<td>Thanks!
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2003Aug/0026.html">Comment</a> from Arve Bersvendsen 07 Aug 2003.
<tr><td>3<td>The specification does not seem to address exactly how aspect
ratios should be queried. The spec seems to assert/dictate that pixel
height divided by pixel width provides the correct device aspect ratio. For some devices, one cannot assume that pixel-height/pixel-width provides
the correct aspect ratio.
<td>Resolved. (See comment 16.)
<!--
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2004Oct/0047">Comment</a> from Jim Wilkinson on Sat, 09 Oct 2004.
<tr><td>x<td>
<p>Section 4.1.5 says "A CSS user agent that encounters
an unrecognized at-rule must ignore the whole of the at-rule and continue
parsing after it." I have to agree with Christian and Jukka on the lack of
precision here ... I'd like to see the following three actions:-
<p>1) A rewording of CSS2.1 Section 4.1.5 to address this point so that it is
clear that the error behaviour of the above case is to ignore the entire
rule, i.e. apply it to no media types. It should also be made clear that
this error behaviour applies if a single (apparent) media type is
unrecognised [or, indeed, all of several], e.g.
<pre>
@media printt { ... }
</pre>
<p>or is invalid (to give a CSS3 Media Queries example):-
<pre>
@media screen (device-width < 640px) { ... }
</pre>
<p>Practically, this will cover typos and also (future) misunderstandings by
authors of media queries. The reworded material might better be
transferred to Section 4.2. I think the original case of a completely
missing media type is the most important since it more probably might be
construed that the rule should then be applied to all media.
<p>2) An addition to CSS2.1 Section 7.2.1 to repeat what the formal grammar
at Appendix G says: that at least one media type must be present (for the
benefit of developers who are unlikely to read and understand the
Appendix).
<p>3) Corresponding changes to the appropriate CSS3 modules.
<p>I would like to be sure that this issue is accepted by the editors of
CSS2.1 and CSS3 and will be closed out in due course. I'm assuming that
that's the function of this list and consistent with W3C's methods for
developing Recommendations. Can one of the editors acknowledge please?
-->
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2004Nov/0016">Comment</a> from Christoph Päper.
<tr><td>4<td>
Regarding CSS 3 Media Queries (CR 2002-07-08), I would like to propose an
additional "media feature" to describe whether or what kind of images are
supported:
<pre>
images (or image)
Value: none | bitmap | vector | all
Applies to: visual media types
Accepts min/max prefixes: no
</pre>
<td>It is an interesting idea to add queries on what features a UA
supports. One could, for example, also add media queries to check
whether a UA supports multi-column layout or CSS3 selectors. This may
become the topic of a future specification, but the CSS WG do not want
to address this big task in a relatively stable draft. Also, it should
be pointed out that UAs have a history of falsifying their identity to
make sure they receive all content.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2005Jul/0291.html">Comment</a> from Anne van Kesteren 07 Jul 2005.
<tr><td>5<td>
Where in CSS3 is defined that @page is allowed in @media as in:
<pre>
@media print{
@page{
margin:2cm;
}
}
</pre>
<p>I couldn't find it anywhere and I guess it should have been defined in CSS 3
media queries which points to CSS 2.1 (or 2.0, actually) which I believe
forbids it. However, the CSS 3 paged media module gives some examples of it
which make it same like it is allowed. (And it would make sense.)
<td>The expectation is that other modules will define this.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2005Jul/0419.html">Comment</a> from Anne van Kesteren Sat, 23 Jul 2005.</a>
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2008Mar/0444.html">Comment</a> from Anne van Kesteren Mon, 31 Mar 2008.</a>
<tr class=a><td>6<td>I was wondering why a negative <length> for 'width' (and other media features)
is not disallowed ... I hope a further revision of the specification could say that "<length> must be
a positive integer when applied to a media feature specified in this
specification." (Perhaps adding "or zero" to that for clarity if needed.)
<td>
With my editor's hat on I went through all the features and clarified what type of "numbers" they could hold and whether those could be negative, zero, or just positive.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2005Dec/0091.html">Comment</a> from Simon Pieters Fri, 16 Dec 2005.
<tr><td>7<td>
I think that if @media has an empty list of media queries, it should be
equivalent to "all". So the following at-rules all have the media query
"all":
<pre>
@media {}
@media all {}
@media "foo" {}
@media all "foo" {}
</pre>
<p>What should happen when the name is the empty string? I guess it should
work the same way as <link rel=stylesheet title=""> in HTML. In Mozilla and
Opera, the empty string is equivalent to no name at all (or the other way
around, no name is equivalent to the empty string). Thus, I think the
following should be equivalent:
<pre>
@media all {}
@media all "" {}
</pre>
<td>We agree that a syntax where 'all' is omitted may be handy. The
revised CR adds a shorthand syntax for media queries that apply to all
media types; the keyword ''all'' can be left out (along with the
trailing ''and''). These two media queries are equivalent:
<pre>
@media all and (orientation: portrait) { ... }
@media (orientation: portrait) { ... }
</pre>
<tr><th class=source colspan=3><a href="http://lists.w3.org/Archives/Public/www-style/2006May/0099">Comment</a> from L. David Baron on Thu, 11 May 2006; <a href="http://lists.w3.org/Archives/Public/www-style/2006Sep/0198.html">answer on www-style</a>.
<tr><td>8<td>
css3-mediaqueries doesn't seem to define the error handling behavior for
syntactically incorrect media queries. This needs to be defined so that
it is possible to know which of the following rules should make p
elements green:
<pre>
@media all and (min-width: 1px), all and (min-width: more than 1px) {
p { color: green }
}
@media all and (min-width: 1px), all and (unknown-feature: 3px) {
p { color: green }
}
@media all and (min-width: 1px), all and (min-width: 1unknownunit) {
p { color: green }
}
@media all and (min-width: 1px), all and ((< min-width 200px)) {
p { color: green }
}
@media all and (min-width: 1px), all and (width at least 200px) {
p { color: green }
}
</pre>
<p>Section 5 does say this:
<blockquote>
Since "max-weight" is an unknown media feature, the Media Query is
false and the associated style sheet will not be applied.
</blockquote>
<p>But it doesn't say how unknown media features are parsed. Is anything
unknown within matched parentheses accepted, but considered always
false?
<td>
<p>This is now clarified in the new error handling section.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2006May/0098.html">Comment</a> from L. David Baron Thu, 11 May 2006.
<tr><td>9<td>Section 4 of http://www.w3.org/TR/2002/CR-css3-mediaqueries-20020708 has
the example:
<pre>
@media screen and (color), projection and (color)
{ @import url(http://www.example.com/color) }
</pre>
even though @import is not allowed inside @media. (Or is that supposed
to be changed in CSS3?)
<td>The example was changed in the editorial revision published <a href="http://www.w3.org/TR/2007/CR-css3-mediaqueries-20070606/">6 June 2007</a>.
<tr><td>10<td>It would also probably be good if some examples in the spec were media
lists on @import rules; this is a good candidate.
<td>Examples using @import rules were added in the editorial revision published <a href="http://www.w3.org/TR/2007/CR-css3-mediaqueries-20070606/">6 June 2007</a>.
<tr>
<th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2006Aug/0204.html">Comment</a> from Christoph Päper on 22 Aug 2006.
<tr><td>11<td>CSS3 Media Queries CR introduces two new units (7.), |dpi| and |
dpcm|, solely for its |resolution| media feature (6.9.). Could this
be changed or at least be amended to also allow standard CSS absolute
length units (e.g. |mm|)? The values using |in| and |cm| would of
course be the respective reciprocals of the current ones and
described the size of one pointW pixel. If a new unit was needed at
all this would be |um|, the ASCII representation of 'µm' for
micrometre, approved by ISO (31?).
<td>The 'dpi' unit is most commonly used to describe resolution, and
'dpcm' provides a SI-based alternative. Adding even more units to
describe resolution seems excessive at this point.
<tr><td>12<td>It might also be a good idea to make this media feature a shorthand
for horizontal and vertical resolution for which separate features
might be added later.
<td>The WG has decided to handle differences in vertical and horizontal resolution as described in comment #3.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Jan/0068.html">Comment</a> from Anne van Kesteren on Mon, 15 Jan 2007.
<tr class=a><td>13<td>
<p>Parsing media queries
<p>In HTML4 it was pretty clear. You first split on the "," and then remove
all characters after the first non ASCII-letter, hyhen or digit. The
resulting values are the media specified.
<p>For Media Queries it's not clear what rules you have to follow when the
media query given (after splitting on ",") doesn't match the syntax. It's
important to know this for the CSSOM MediaList interface for instance.
<p><em>After reading the reply to comment #8, Anne writes: Ah ok, I guess
that sort of solves it. It does mean though that "not all and
(foobar)" would apply. Is that desirable? I was thinking that such a
media query should perhaps simply be ignored completely so we don't
have to worry about how to represent it in the DOM either. That seems
also more in line with error handling in CSS.</em>
<td>
This is now addressed by the revised syntax section.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Aug/0077.html">Comment</a> from fantasai Mon, 13 Aug 2007.
<tr class=r><td>14<td>
<p>The poster suggested that it would be more useful to use the media *groups*
defined in CSS2.1 [1]. E.g.
<pre>
@media paged { ... }
</pre>
<td>Too late for this version. We should reconsider this for Media Queries Level 4.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Aug/0101.html">Comment</a> from fantasai Tue, 21 Aug 2007.
<tr class=r><td>15<td>
Today we discussed how imprecision in device hardware results in
display widths and heights that are not *exactly* in line with the
nominal width and height. It was suggested that we should allow
some fuzz factor in media query matching for this reason.
<td>No change.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Aug/0097.html">Comment</a> from fantasai Tue, 21 Aug 2007.
<tr class=a><td>16<td>
<pre>
Proposed changes:
http://www.w3.org/TR/css3-mediaqueries/#device-aspect-ratio
# In this specification, aspect ratio is defined as the number of
# horizontal pixels over the number of vertical pixels.
change to
| In this specification, aspect ratio is defined as the horizontal
| length of the device's display divided by its vertical length.
http://www.w3.org/TR/css3-mediaqueries/#resolution
# The 'resolution' media feature describes the resolution of the
# output device, i.e. the density of the pixels.
Add
| When querying devices with non-square pixels, in 'min-resolution'
| queries the least-dense dimension must be compared to the specified
| value and in 'max-resolution' queries the most-dense dimensions must
| be compared instead. A fixed 'resolution' query never matches a device
| with non-square pixels.
(Alternatively we could allow two values to query each dimension
independently, but I don't think this is useful.)
</pre>
<td>Accepted.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Aug/0119.html">Comment</a> from Stewart Brodie Wed, 22 Aug 2007.
<tr class=a><td>17<td>
<pre>
'not' and unknown media types:
Section 3 says: "The presence of the keyword 'not' at the beginning of the
query negates the results." Section 4 says: "Media queries involving
unknown media types are always false".
When I read that, the word 'always' led me to wonder whether or not unknown
media types trump the section 3 definition of 'not'. I suggest the
following clarifications:
1) remove the word "always" from the section 4 statement
2) Add an example showing that the following media query is true:
@media not 3d-glasses { ... }
</pre>
<td>
'not foo' is true and 'foo' is false. (3d-glasses is a parse error.)
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Aug/0120.html">Comment</a> from Stewart Brodie Wed, 22 Aug 2007.
<tr class=a><td>18<td>
Does "color-index" have a zero value unless a lookup table is used?
<td>
If the device does not use a color lookup table, the value is zero.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Aug/0201.html">Comment</a> from Andrew Fedoniouk Tue, 28 Aug 2007.
<tr class=r><td>19<td>
<p>Is it possible to add in media queries [1] value that will
indicate that UA is running with high-contrast-screen settings?
<td>Too late for this version. We should reconsider this for Media Queries Level 4.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Nov/0065.html">Comment</a> from Ian Hickson 6 Nov 2007
<tr class=a><td>20<td>
<p>it'd be nice if we defined the lack of a media query string to mean "all"
<td>Yes.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Nov/0125.html">Comment</a> from Henri Sivonen 14 Nov 2007.
<tr class=a><td>21<td>
<p>Parsing is not well defined in terms of whitespace and error handling.
<td>This is now addressed by the syntax section.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Nov/0209.html">Comment</a> from Henri Sivonen 17 Nov 2007.
<tr class=r><td>22<td>
<p>If a media feature does not match the media type is that an error?
<td>No. Writing "speech and (width:100px)" is acceptable. The validator may issue a warning though.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Nov/0212.html">Comment</a> from Henri Sivonen 17 Nov 2007.
<tr class=a><td>23<td>
<p>grid doesn't apply to all media
<td>Fixed, thanks!
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Dec/0005.html">Comment</a> from Anne van Kesteren 03 Dec 2007.
<tr class=r><td>24<td>
<p>I think that the Media Queries draft
http://www.w3.org/TR/2007/CR-css3-mediaqueries-20070606/ should either
define media types itself or should reference CSS 2.1 for them.
Referencing HTML4 and CSS2 for these seems outdated. For instance, "aural"
is deprecated in CSS 2.1, but "speech" is not. "speech" is not mentioned
in Media Queries and "aural" is used in examples and mentioned several
times.
<td>Too late for this version. We should reconsider this for Media Queries Level 4.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Dec/0038.html">Comment</a> from Anne van Kesteren 10 Dec 2007.
<tr class=a><td>25<td>Syntax issues.
<td>Addressed. (Syntax is now described in terms of CSS 2.1 eliminating these issues.)
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Dec/0051.html">Comment</a> from Anne van Kesteren 12 Dec 2007.
<tr class=a><td>26<td>Using the same syntax rules for HTML and CSS.
<td>Addressed by using <a href="http://lists.w3.org/Archives/Public/www-style/2008Feb/thread.html#msg35">Bert's syntax proposal</a>.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Dec/0119.html">Comment</a> from Simon Proctor 19 Dec 2007
<tr class=r><td>27<td>
Introducing a 'supports()' querying feature.
<td>Too late for this version. We should reconsider this for Media Queries Level 4.
<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/20080406181816.GA25391@ridley.dbaron.org">Comment</a> from David Baron 06 Apr 2008
<tr class=a><td>28<td>
What does '(scan)' mean?
<td>The draft is clarified to mention that each media feature (including min/max prefixed)
"(media-feature)" is equivalent to "(media-feature:x)" for when x is not equal to 0. (If media-feature does not accept 0 x can be any value.)
<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/20080407041829.GA18449@ridley.dbaron.org">Comment</a> from David Baron 07 Apr 2008
<tr class=a><td>29<td>
Bad examples for orientation. (Only value was given.)
<td>Examples are fixed.
<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/20080407040008.GA17448@ridley.dbaron.org">Comment</a> from David Baron 07 Apr 2008
<tr class=a><td>30<td>
Is 'resolution' in terms of CSS or device pixels?
<td>Should be device pixels.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2008Apr/0457.html">Comment</a> from fantasai 24 Apr 2008
<tr class=a><td>31<td>
Definitions of 'height' / 'width' / 'device-height' / 'device-width' need rewording.
<td>Reworded as suggested later in the thread.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2008Jun/0045.html">Comment</a> from Stewart Brodie 6 Jun 2008
<tr class=a><td>32<td>
Does the 'resolution' feature take a float or integer?
<td>Defined <resolution> to take an <float> immediately followed by a unit identifier per <a href="http://www.w3.org/mid/4856E023.9010003@inkedblade.net">this e-mail from fantasai</a>.
<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/484D9F48.80405@inkedblade.net">Comment</a> from fantasai 9 Jun 2008
<tr class=r><td>33<td>
Do we need special wording for display-level transformations, like zooming and N-up printing?
<td>We're not going into this level of detail for now.
<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/20080611215625.GA30548@pickering.dbaron.org">Comment</a> from David Baron 11 Jun 2008
<tr class=a><td>34<td>
Allow whitespace around '/' for the aspect-ratio and device-aspect-ratio media features.
<td>Agreed.
<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/20080618220428.GA10229@pickering.dbaron.org">Comment</a> from David Baron 19 Jun 2008
<tr class=a><td>35<td>
<pre>http://dev.w3.org/csswg/css3-mediaqueries/#media1 says:
# For a media feature feature, (feature) will evaluate to true if
# (feature:x) will evaluate to true for a value x other than zero.
Does this mean:
(a) (width) is always true, even if the viewport width is zero,
because "0px" is a value other than zero, or:
(b) (width) is false when the viewport width is zero because "0px"
and "0" are both not "other than zero"?
I'd also note that because specified widths cannot be negative,
(max-width) currently behaves the same as (width), whereas
(min-width) is always true. Is that really intended?</pre>
<td>Zero is clarified to mean 0px, 0, etc. <a href="http://lists.w3.org/Archives/Public/www-style/2008Sep/0002.html">Min/max prefixed media features without values cannot be used</a>.
<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/20080619203334.GA30094@pickering.dbaron.org">Comment</a> from David Baron 19 Jun 2008
<tr class=a><td>36<td>
<pre>After reading http://dev.w3.org/csswg/css3-mediaqueries/#grid it's
not clear to me whether the queries "(grid: -1)" or "(grid: 2)"
should be parse errors or should always be false. It should be
clear.</pre>
<td><a href="http://www.w3.org/mid/op.ughpofcf64w2qv@annevk-t60.oslo.opera.com">Clarified</a> they are indeed parse errors.
<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2008Oct/0328.html">Comment</a> from Dean Jackson 30 Oct 2008
<tr class=r><td>37<td>The request is changing the syntax of aspect-ratio and
device-aspect-ratio to floats and orientation to angles.
<td>The WG decided to not make a change here. The WG also decided to keep aspect-ratio and device-aspect-ratio and not drop them as suggested in the follow-up thread.
<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/9fbcac550809220609g484b1ef3l7c4fbe9908b3d6dc@mail.gmail.com">Comment</a> from Jens Meiert 22 Sep 2008
<tr class=a><td>38<td>Editorial.
<td>Fixed.
<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/48FF5CA3.5070406@xwiki.com">Comment</a> from Sergiu Dumitriu 23 Oct 2008
<tr class=a><td>39<td>Editorial comments. Also a question whether 'ex' should be described for tty since 'em' is defined.
<td>The WG decided to remove the definition of 'em' for tty and leave that definition up to the values & units draft.
<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/Pine.LNX.4.63.0902242324240.6949@master.abisoft.spb.ru">Comment</a> from Andrey Mikhalev 25 Feb 2009
<tr class=a><td>40<td>The grammar mixes CSS2 grammar and CSS core grammar productions.
<td>Fixed by using expr rather than value.
<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/op.ulukkazr64w2qv@annevk-t60.oslo.opera.com">Comment</a> from Anne van Kesteren 8 Dec 2008
<tr class=a><td>41<td>Media queries has the implied suggestion to violate core grammar error handling.
<td>Added a note of a clarification per fantasai's suggestion.
<!--
http://lists.w3.org/Archives/Public/www-style/2005Jul/0414.html
6.2. height typo
FIXED, outright error
http://lists.w3.org/Archives/Public/www-style/2003Dec/0016
NO, just a qutstion
http://lists.w3.org/Archives/Public/www-style/2002Jul/0089.html
http://lists.w3.org/Archives/Public/www-style/2002Jul/0088.html
NO
http://lists.w3.org/Archives/Public/www-style/2002Jul/0075
I found a few grammatical errors
EDITORIAL
http://lists.w3.org/Archives/Public/www-style/2002Jul/0006
Small errors I noticed:
EDITORIAL
http://lists.w3.org/Archives/Public/www-style/2002Mar/0073
IRRELEVANT
http://lists.w3.org/Archives/Public/www-style/2002Mar/0022
http://lists.w3.org/Archives/Public/www-style/2002Feb/0151
I attach my comments on the Last Call Working Draft of Media Queries
DISCUSS
http://lists.w3.org/Archives/Public/www-style/2002Feb/0157
WAI/PF comments
EDITORIAL?
http://lists.w3.org/Archives/Public/www-style/2002Feb/0145
EDITORIAL
http://lists.w3.org/Archives/Public/www-style/2002Feb/0117
EDITORIAL
http://lists.w3.org/Archives/Public/www-style/2002Feb/0048
CREDIT, suggests dpcm,
http://lists.w3.org/Archives/Public/www-style/2001Apr/0025
CREDIT, from RIJK, credit
CSS-WG
http://lists.w3.org/Archives/Member/w3c-css-wg/2006AprJun/0126.html
media queries syntax
http://lists.w3.org/Archives/Member/w3c-css-wg/2006AprJun/0153
-->
</table>
You can’t perform that action at this time.