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

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

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 09 Jan 2014 13:02:50 -0500
Message-ID: <52CEE44A.8000307@mit.edu>
To: Erik Arvidsson <arv@chromium.org>
CC: "public-script-coord@w3.org" <public-script-coord@w3.org>
On 1/9/14 12:54 PM, Erik Arvidsson wrote:

 > I'm in favor of the IE/Safari behavior.

Sounds good.  I'll work on updating the spec accordingly.

> However, I don't want us to introduce a new extended attribute for this.

We already have [TreatNonCallableAsNull], which is only used by event 
handlers so far.  I plan to just change its behavior and rename to 
[TreatNonObjectAsNull], not introduce any new weirdness we don't already 

> If people use prefixed code incorrectly in a global scope I'm
> willing to break them in the name of saner web platform.

I'll believe it when I see Blink actually removing some of the prefixed 
properties in question.  We tried that in Gecko, and ended up with 
widespread breakage, such that we could not ship the change.  I'm not 
willing to experiment with that again, given the amount of time that was 
wasted previously and my low estimate of the chance of ever being able 
to ship such a change.

Further, this is a problem for common polyfill techniques too, not just 

Received on Thursday, 9 January 2014 18:03:19 UTC

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