W3C home > Mailing lists > Public > www-style@w3.org > February 2015

Re: [CSS21] Ambiguity in tokenizer, "normative appendix G"

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 3 Feb 2015 19:48:09 -0800
Message-ID: <CAAWBYDB1hqPc9Cv6VRqcv7hqizsyK-wVCOkd+sTSqFu=OgG_Kw@mail.gmail.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Cc: www-style list <www-style@w3.org>
On Tue, Feb 3, 2015 at 12:18 PM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:
> Hi,
>
>   In http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#syntax
> "These descriptions are normative. They are also complemented by the
> normative grammar rules presented in Appendix G." but Appendix G is
> marked "This appendix is non-normative." so that doesn't make sense.
>
> In 4.1.1. the specification apparently fails to say whether variations
> of `url(` at the end of the input are FUNCTION or BAD_URI tokens. They
> should probably be BAD_URI tokens.
>
> The CSS 2.2 draft has the same problems.

As Zack says, all of the CSS2 grammar has been superseded by CSS Syntax.

It's quite easy to trace the execution of the spec's tokenizer.  In
particular, "consume an ident-like token" will eat the `url(`, then
send you down the "consume a url token" algo, which immediately hits
the EOF and returns a (valid) url token with an empty url.

~TJ
Received on Wednesday, 4 February 2015 03:48:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:01 UTC