The global object in browsers

Ian Hickson ian at
Thu Feb 19 02:10:50 PST 2009

On Thu, 19 Feb 2009, David-Sarah Hopwood wrote:
> Ian Hickson wrote:
> > On Tue, 17 Feb 2009, Mark Miller wrote:
> >> On Tue, Feb 17, 2009 at 5:03 PM, Ian Hickson <ian at> wrote:
> >>> Indeed, I noted this earlier. The behavior HTML5 codifies is the 
> >>> behavior that the majority of browser vendors have asked me to codify.
> >> Majority, huh? Which vendors? How does the behavior they ask for 
> >> correlate with what their browsers do?
> > 
> > Opera, Apple, and Mozilla. The HTML5 spec originally specced what IE 
> > does, namely throw an exception when running code whose global object 
> > doesn't match the current Window object, but Opera, Apple, and Mozilla 
> > rejected this on the grounds that it could not be implemented in a 
> > high-performance manner.
> That is clearly false. It would be a single pointer comparison when 
> entering a new context.
> I make no comment here on whether this behaviour would be a good idea on 
> other criteria, just that rejecting it on performance grounds is absurd.

To be honest it doesn't really matter to me what the reason is -- if three 
browser vendors tell me they're not implementing the spec, I change the 
spec. My goal is to have a specification that browser vendors implement.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

More information about the Es-discuss mailing list