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

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

From: <bugzilla@jessica.w3.org>
Date: Fri, 02 May 2014 13:45:32 +0000
To: public-script-coord@w3.org
Message-ID: <bug-24959-3890-zwZmcnS0si@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24959

--- Comment #8 from Christophe Dumez <dchris@gmail.com> ---
(In reply to Dirk Schulze from comment #7)
> (In reply to Christophe Dumez from comment #6)
> > (In reply to Dirk Schulze from comment #5)
> > > (In reply to Nils Barth from comment #4)
> > > > Thanks Dirk: yup, the other alternative is to use a different separator.
> > > > 
> > > > In Blink, we use | or & for separating (depending on which is clearer in
> > > > context); probably cleaner-looking would be ; as suggested by OP, though I
> > > > think a tuple with commas (..., ...) is probably clearer still.
> > > 
> > > I fear that the grammar gets more complex. So far it is just Exposed that
> > > has this issue (at least in the WebIDL spec).
> > 
> > Actually, [Global] has the same issue:
> > [Global=Worker,DedicatedWorker]
> 
> No condition nesting so far.

That's right. I was just saying that [Exposed] and [Global] have the same
issue. I am personally in favor of using another separator than the comma. We
use the ampersand ('&') in Blink and I think this is fine.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 2 May 2014 13:45:37 UTC

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