W3C home > Mailing lists > Public > www-style@w3.org > January 2013

Re: [css3-syntax] EOF and } in at-rule preludes and selectors

From: Glenn Adams <glenn@skynav.com>
Date: Tue, 29 Jan 2013 16:30:42 -0700
Message-ID: <CACQ=j+d1Lkdzx=pnbLQiAx7RGTBAny1Zgrw7Jjzpq0J-red1nw@mail.gmail.com>
To: Simon Sapin <simon.sapin@kozea.fr>
Cc: "www-style@w3.org" <www-style@w3.org>
On Tue, Jan 29, 2013 at 3:32 PM, Simon Sapin <simon.sapin@kozea.fr> wrote:

> Hi,
>
> A few edge cases:
>
> * EOF in selector mode should be a parse error (a {} block is missing)
> * EOF in at-rule prelude should be like ';'. A parse error for
> declarations-filled or rule-filled at-rules, but not for other at-rules:
>
> data:text/html,<style>@import "data:text/css,body{**background:green"
>
> In the example above the @import rule is valid even though it ends with
> EOF rather than ';'
>

I would not agree this is valid. Rather, its operation depends on
interoperable error handling behavior.


>
> * '}' in either mode should be like EOF, but *only* if this is nested in a
> matching '{' block such as @media {
> * An unpaired '}' in a top-level selector or at-rule prelude should be
> like ']'. It’s preserved token as far as Syntax is concerned, it’s only
> invalid in Selectors, MQ, etc.
>
>
> Maybe this last distinction is what "If the stack of open rules has three
> or more items on it, …" was about?
>
>
> --
> Simon Sapin
>
>
Received on Tuesday, 29 January 2013 23:31:30 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:04 GMT