@@ -679,7 +679,8 @@ <h3 id=error><span class=secno>3.1 </span>Error Handling</h3>
679679 until the end of the media query, while observing < a
680680 href ="http://www.w3.org/TR/CSS21/syndata.html#block "> the rules for
681681 matching pairs</ a > of (), [], {}, "", and '', and correctly handling
682- escapes. < a href ="#CSS21 " rel =biblioentry > [CSS21]<!--{{!CSS21}}--> </ a > </ p >
682+ escapes. Media queries with unexpected tokens are ignored. < a
683+ href ="#CSS21 " rel =biblioentry > [CSS21]<!--{{!CSS21}}--> </ a > </ p >
683684
684685 < div class =example >
685686 < pre > @media (example, all,), speech { /* only applicable to speech devices */ }
@@ -693,20 +694,18 @@ <h3 id=error><span class=secno>3.1 </span>Error Handling</h3>
693694
694695 < pre > @media all and(color) { ... }</ pre >
695696 </ div >
696- <!--
697- Removed as this might cause the wrong style sheet to apply if a part of the
698- media query is missing. This will now cause the respective media query to
699- be ignored per the previous rule.
700-
701- <li>
702- <p><strong>Unexpected end of media query.</strong> User agents are to
703- close all open constructs (such as parenthesis and curly braces) upon
704- encountering an unexpected end of a media query.</p>
705-
706- <p class="note">This error handling condition is only meaningful outside
707- of CSS.</p>
708- -->
709-
697+
698+ < p > When all media queries in a media query list are ignored it is the
699+ same as if "< code > not all</ code > " was specified.</ p >
700+
701+ < div class =example >
702+ < p > The following lists of media queries would all end up as "< code > not
703+ all</ code > ":</ p >
704+
705+ < pre > @media test, @test { ... }
706+ @media example { ... }
707+ @media screen and (min-example), example { ...}</ pre >
708+ </ div >
710709 </ ul >
711710
712711 < h2 id =media1 > < span class =secno > 4. </ span > Media features</ h2 >
0 commit comments