W3C home > Mailing lists > Public > public-html@w3.org > February 2009

Re: window.onerror initial value

From: Ian Hickson <ian@hixie.ch>
Date: Fri, 13 Feb 2009 02:19:52 +0000 (UTC)
To: Simon Pieters <simonp@opera.com>
Cc: public-html <public-html@w3.org>
Message-ID: <Pine.LNX.4.62.0902130218570.28232@hixie.dreamhostps.com>

On Tue, 27 Jan 2009, Simon Pieters wrote:
> 
> The spec says about window.onerror:
> 
> "The initial value of onerror must be undefined."
> 
> I note that in IE8 RC1 and WebKit window.onerror is null.
> 
> What's the reason for saying it must be undefined?

There was previously a difference between onerror == null and onerror == 
undefined. However, testing shows that this is not well or widely 
implemented, so I've simplified this part of the spec and made onerror 
just a regular old Function event handler attribute like the others 
(except with more arguments in some cases).

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 13 February 2009 02:20:27 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:01 UTC