Ran a quick test on Opera and IE along these lines:
htmlbodyscript function onload() { alert(onload); }
/script/body/html
Only firefox displayed the alert dialog when loading this page -
IE/Opera/WebKit do not. So if this behavior is incorrect, at least we have
lots of company.
-atw
On Sun, Jul
You might want to ask someone at Mozilla if they'd be willing to
change their behavior to match everyone else. The whatwg might be a
good forum for that if you're not sure who to contact individually.
Adam
On Mon, Jul 20, 2009 at 6:30 PM, Drew Wilsonatwil...@google.com wrote:
Ran a quick test
You should test the same thing with window.onload. If I recall
correctly, you'll see similar inoperability.
Adam
On Sun, Jul 19, 2009 at 9:29 AM, Drew Wilsonatwil...@google.com wrote:
I was writing a new worker unit test and I noticed that all of our unit
tests set event handlers in worker
Yes, it happens with window.onload() too (I didn't mean to imply that it was
a worker-only issue).
This seems like precisely the type of inoperability that the HTML5 spec
should address, but I figured I should get some input here before bringing
it up there.
-atw
On Sun, Jul 19, 2009 at 10:31
I think we should do what Firefox does in the window.onload case. :)
I'm not familiar with the history through. Is there some particular
reason we have our current behavior?
Adam
On Sun, Jul 19, 2009 at 10:56 AM, Drew Wilsonatwil...@google.com wrote:
Yes, it happens with window.onload() too
On Jul 19, 2009, at 11:10 AM, Adam Barth wrote:
I think we should do what Firefox does in the window.onload case. :)
I'm not familiar with the history through. Is there some particular
reason we have our current behavior?
The current behavior is an accident of implementation, but I think
6 matches
Mail list logo
