@@ -101,16 +101,30 @@ <h2>13.2 <a name="page-box">Page boxes</a>: the @page rule</h2>
101101< P > Authors can specify the margins of a page box inside an < a name ="x3 "> < span
102102class ="index-def " title ="@page "> @page</ span > </ a > rule. An @page rule
103103consists of the keyword "@page", followed by an optional page
104- selector, followed by a block of declarations. The declarations in an
104+ selector, followed by a block containing declarations and
105+ at-rules. The declarations in an
105106@page rule are said to be in the < span class ="index-def "
106107title ="page-context "> < a name ="page-context "> < dfn > page
107108context</ dfn > </ a > </ span > .</ p >
108109
110+ < p class =note > Note: CSS level 2 has no at-rules that may appear
111+ inside @page, but such at-rules are expected to be defined in
112+ level 3.
113+
109114< P > The < a name ="x5 "> < span class ="index-def " title ="page selector "> < dfn > page
110115selector</ dfn > </ span > </ a > specifies for which pages the declarations
111116apply. In CSS 2.1, page selectors may designate the first page,
112117all left pages, or all right pages</ p >
113118
119+ < P > The rules for handling malformed declarations, malformed
120+ statements, and invalid at-rules inside @page are as defined in < a
121+ href ="syndata.html#parsing-errors "> section 4.2,</ a > with the
122+ following addition: when the UA expects the start of a declaration or
123+ at-rule (i.e., an IDENT token or an ATKEYWORD token) but finds an
124+ unexpected token instead, that token is considered to be the first
125+ token of a malformed declaration. I.e., the rule for malformed
126+ declarations, rather than malformed statements is used to determine
127+ which tokens to ignore in that case.
114128
115129< h3 > 13.2.1 < a name ="page-margins "> Page margins</ a > </ h3 >
116130
0 commit comments