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: Garrett Smith <dhtmlkitchen@gmail.com>
Date: Thu, 26 Dec 2013 10:34:45 -0800
Message-ID: <CABZUbM2Wr-OCmaCEuOeKmpCRxcBKS7-saiqoD23GFMvOynm4hw@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: "public-script-coord@w3.org" <public-script-coord@w3.org>
On 12/26/13, Boris Zbarsky <bzbarsky@mit.edu> 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].
>
That allows for legacy support of:
addEventListener("click", {handleEvent: function(ev) { } }, true);


> 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?
>
Sounds good.
-- 
Garrett
@xkit
ChordCycles.com
garretts.github.io
Received on Thursday, 26 December 2013 18:35:13 UTC

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