@@ -502,10 +502,12 @@ <h4>Principles of CSS error handling</h4>
502502initial stream of the tokens resulting from the < a
503503href ="#tokenization "> tokenization process</ a > that can be parsed
504504according to the grammar presented in this chapter. (For example, if a
505- brace opening a declaration block < span class ="issue "> [link-ify
505+ brace closing a declaration block < span class ="issue "> [link-ify
506506this]</ span > is not present, the declaration block
507507must be ignored since the closing brace is required to satisfy this
508- grammar.)</ p >
508+ grammar.) < span class ="issue "> [This might lead to highly unexpected
509+ behavior when there's an extra closing brace (etc.). Do we really want
510+ this?]</ span > </ p >
509511
510512< p > Some of the constraints of CSS are not expressed in the grammar. For
511513example, an < code > @charset</ code > rule is not permitted in an embedded
@@ -1126,7 +1128,11 @@ <h4 id="media-types">Recognized media types</h4>
11261128< p > A CSS < span class ="index-def " title ="media type "> < dfn > media
11271129type</ dfn > </ span > names a set of CSS properties. A user agent that
11281130claims to support a media type by name must implement all of the
1129- properties that apply to that media type.
1131+ properties that apply to that media type. < span class ="issue "> [This
1132+ needs to be relaxed to deal with profiles.]</ span > (For the 'all' media
1133+ type, this means that it must support all properties that apply to all
1134+ media types. < span class ="issue "> [Should all be removed from the list
1135+ and separated to make this more logical?]</ span > )</ p >
11301136
11311137< p > The names chosen for CSS media types reflect target devices for
11321138which the relevant properties make sense. In the following list of CSS
0 commit comments