Obsolete
Status Update
Comments
gr...@gmail.com <gr...@gmail.com> #2
[Comment Deleted]
gr...@gmail.com <gr...@gmail.com> #3
[Comment Deleted]
gr...@gmail.com <gr...@gmail.com> #4
[Comment Deleted]
gr...@gmail.com <gr...@gmail.com> #5
[Comment Deleted]
gr...@gmail.com <gr...@gmail.com> #6
[Comment Deleted]
gr...@gmail.com <gr...@gmail.com> #7
[Comment Deleted]
gr...@gmail.com <gr...@gmail.com> #8
[Comment Deleted]
gr...@gmail.com <gr...@gmail.com> #9
[Comment Deleted]
gr...@gmail.com <gr...@gmail.com> #10
[Comment Deleted]
gr...@gmail.com <gr...@gmail.com> #11
[Comment Deleted]
gr...@gmail.com <gr...@gmail.com> #12
[Comment Deleted]
gr...@gmail.com <gr...@gmail.com> #13
[Comment Deleted]
gr...@gmail.com <gr...@gmail.com> #14
Onload works, sorry.
But, there happens to be a new bug found.
It wasn't the onload event causing the issues, it was the fact that the DOM isn't
ready when readyState == "complete".
When there is a setTimeout of 1 millisecond, the DOM is finally ready after the
readyState == "complete".
But, there happens to be a new bug found.
It wasn't the onload event causing the issues, it was the fact that the DOM isn't
ready when readyState == "complete".
When there is a setTimeout of 1 millisecond, the DOM is finally ready after the
readyState == "complete".
gr...@gmail.com <gr...@gmail.com> #15
DOM gives a documentElement.nodeName of "HTML" with no children for the first
millisecond of readyState == "complete". Very strange.
millisecond of readyState == "complete". Very strange.
[Deleted User] <[Deleted User]> #16
[Empty comment from Monorail migration]
[Deleted User] <[Deleted User]> #17
[Deleted User] <[Deleted User]> #18
gl...@gmail.com <gl...@gmail.com> #19
uTest
Repro in dev build: Y
Repro in stable build: Y
Accurate Steps: Y
Configuration used: 5.0.375.70 + 6.0.437.3 + Windows 7 x64
Looks to be reproducible. Need more info from the OP in terms of actual pages that this occurs.
Repro in dev build: Y
Repro in stable build: Y
Accurate Steps: Y
Configuration used: 5.0.375.70 + 6.0.437.3 + Windows 7 x64
Looks to be reproducible. Need more info from the OP in terms of actual pages that this occurs.
la...@chromium.org <la...@chromium.org> #20
[Empty comment from Monorail migration]
bl...@gmail.com <bl...@gmail.com> #21
"Onload works, sorry."
Not for me. I'm not getting load events on iframes in Chrome 10.0.648.205.
Not for me. I'm not getting load events on iframes in Chrome 10.0.648.205.
[Deleted User] <[Deleted User]> #22
[Deleted User] <[Deleted User]> #23
[Deleted User] <[Deleted User]> #24
bu...@chromium.org <bu...@chromium.org> #25
Closing old bug as obsolete. Please file a new bug (with details) if this problem is still occurring for you.
bu...@chromium.org <bu...@chromium.org> #26
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
bu...@chromium.org <bu...@chromium.org> #27
[Empty comment from Monorail migration]
Description
Chrome Version : 3.0.195.38http://beta.grantgalitz.com/pictures.php
URL :
Behavior in Safari 3.x/4.x : BAD
Behavior in Firefox 3.x: OK
Opera: BAD
IE 7+: OK
SEVERE DOM EVENT BUG IN WEBKIT
What steps will reproduce the problem?
onload event attached to it.
Note: The document loaded by the form is an XML document which does load
into the frame, as seen by the dev tools, but fails to trigger an onload event.
Note: The webpage is an application/xhtml+xml webpage set with the xhtml
1.1 doctype.