8000 update sotd text, remove bogus claim · w3c/csswg-drafts@801eec1 · GitHub
Skip to content

Commit 801eec1

Browse files
annevkannevk
committed
update sotd text, remove bogus claim
1 parent c663a1e commit 801eec1

3 files changed

Lines changed: 31 additions & 5 deletions

File tree

‎css3-mediaqueries/Overview.html‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -189,10 +189,10 @@ <h2 class="no-num no-toc" id=status>Status of this document</h2>
189189
</dl>
190190

191191
<li>
192-
<p>A minimum of another three months of the CR period must elapse. That
193-
is, this specification will not exit CR before 01 September 2007. When
194-
the specification exits CR, an implementation report will be published.
195-
At this point, no such report exists.
192+
<p>A minimum of another three months of the CR period must elapse.
193+
<!--That is, this specification will not exit CR before 23 August 2008.-->
194+
When the specification exits CR, an implementation report will be
195+
published. At this point, no such report exists.
196196

197197
<li>
198198
<p>The specified technology must not be harmful for accessibility.

‎css3-mediaqueries/Overview.src.html‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,10 @@ <h2 class="no-num no-toc" id="status">Status of this document</h2>
128128
specifically designed to pass the test suite and not intended for
129129
daily usage going forward).</li></ol></dd></dl></li>
130130

131-
<li><p>A minimum of another three months of the CR period must elapse. That is, this specification will not exit CR before 01 September 2007. When the specification exits CR, an implementation report will be published. At this point, no such report exists.</p></li>
131+
<li><p>A minimum of another three months of the CR period must elapse.
132+
<!--That is, this specification will not exit CR before 23 August 2008.-->
133+
When the specification exits CR, an implementation report will be
134+
published. At this point, no such report exists.</p></li>
132135

133136
<li><p>The specified technology must not be harmful for
134137
accessibility.</p></li></ol>

‎css3-mediaqueries/disposition.html‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -628,6 +628,29 @@ <h1>Disposition of comments for Media Queries CR</h1>
628628

629629
<td class=proposal>Agreed.
630630

631+
<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
632+
<tr><td>35<td>
633+
<pre>http://dev.w3.org/csswg/css3-mediaqueries/#media1 says:
634+
# For a media feature feature, (feature) will evaluate to true if
635+
# (feature:x) will evaluate to true for a value x other than zero.
636+
637+
Does this mean:
638+
639+
(a) (width) is always true, even if the viewport width is zero,
640+
because "0px" is a value other than zero, or:
641+
642+
(b) (width) is false when the viewport width is zero because "0px"
643+
and "0" are both not "other than zero"?
644+
645+
I'd also note that because specified widths cannot be negative,
646+
(max-width) currently behaves the same as (width), whereas
647+
(min-width) is always true. Is that really intended?</pre>
648+
649+
<td class=proposal>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>.
650+
651+
652+
653+
631654
<!--
632655
633656

0 commit comments

Comments
 (0)