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

Re: [TreatNonCallableAsNull] extended attribute

From: Marcos Caceres <w3c@marcosc.com>
Date: Wed, 20 Jun 2012 10:12:23 +0100
To: Cameron McCormack <cam@mcc.id.au>
Cc: Anssi Kostiainen <anssi.kostiainen@nokia.com>, public-script-coord@w3.org, ext Mounir Lamouri <mounir@lamouri.fr>
Message-ID: <BAC13ED4C4B84097BC1A73FF03615622@marcosc.com>

On Wednesday, 20 June 2012 at 04:03, Cameron McCormack wrote:

> Anssi Kostiainen:
> > As per the guidance in the Web IDL spec [1], I'd like to let you know we're using [TreatNonCallableAsNull] in the Battery Status API spec [2] which is transitioning to CR.
> >  
> > Our understanding is that until we have a lowercase function keyword (or something equivalent), we'll depend on [TreatNonCallableAsNull].
> >  
> > The spec has multiple independent implementations, some of which are in the wild already.
> Thanks for notifying the list. As it is for consistency with legacy  
> behaviour – i.e. to have all event handler IDL attributes  
> [TreatNonCallableAsNull] – it's fine to use it.
> I've mailed www-dom with my request to include a definition that  
> everyone can use instead of the awkward "[TreatNonCallableAsNull]  
> attribute Function":
> http://lists.w3.org/Archives/Public/www-dom/2012AprJun/0163.html  
Seems Anne rejected it… and I don't think a bug was ever filed on HTML, so I filed one:


Kind regards,
Received on Wednesday, 20 June 2012 09:13:01 UTC

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