W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2014

[Bug 24959] "Exposed=Window,Worker" will be parsed to 2 extended attributes

From: <bugzilla@jessica.w3.org>
Date: Fri, 25 Jul 2014 17:46:33 +0000
To: public-script-coord@w3.org
Message-ID: <bug-24959-3890-6rnz3bneFF@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24959

Boris Zbarsky <bzbarsky@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #17 from Boris Zbarsky <bzbarsky@mit.edu> ---
Though, the grammar rules in the spec are no longer one-token lookahead.  This
is what the spec has, basically:

ExtendedAttributeIdent    →    identifier "=" identifier
ExtendedAttributeIdentList    →    identifier "="
IdentOrParenthesizedIdentifierList
IdentOrParenthesizedIdentifierList    →    identifier
 | "(" IdentifierList ")"

So [Foo=Bar] it's ambiguous: is that an ExtendedAttributeIdent or an
ExtendedAttributeIdentList without the parens?

It's not clear to me why we can't just allow the Exposed extended attribute
value to match either ExtendedAttributeIdent or ExtendedAttributeIdentList and
then require the latter to be parenthesized.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 25 July 2014 17:46:38 UTC

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