W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2013

Re: Spec for [Global] does not seem to be quite web-compatible, and none of the UAs are really compatible with each other

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Fri, 27 Dec 2013 15:42:07 +0200
Message-ID: <52BD83AF.1090006@helsinki.fi>
To: Boris Zbarsky <bzbarsky@MIT.EDU>, "public-script-coord@w3.org" <public-script-coord@w3.org>
On 12/26/2013 06:12 PM, Boris Zbarsky wrote:
> On 12/22/13 1:31 AM, Boris Zbarsky wrote:
>> Any other bright ideas?
> Cameron suggested just implementing the Safari behavior here.  Specifically:
> 1)  Come up with a new extended attribute to replace [TreatNonCallableAsNull].  Maybe [TreatNonObjectAsNull].
> 2)  When [TreatNonObjectAsNull] is used, which would only be for event handlers, treat non-objects as null, but allow any object, whether callable or
> not.
> 3)  When invoking the event handler, just do nothing (and pretend the return value of the call was undefined) if the object is not callable.
> 4)  Leave the on* properties directly on the global.
> The more I think about this, the more it seems to me like the way to go.
> Anyone objecting?
> -Boris

I prefer this approach.

Though it is not quite clear to me why we need TreatNonObjectAsNull. Could we possibly
make EventHandlers 'any', and call them only if they are callable.

Received on Friday, 27 December 2013 13:42:41 UTC

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