[Webkit-unassigned] [Bug 30765] New: Nightly build of Safari and Chrome 4 remove two functions registered to window.onload event when calling removeEventListener to remove the first one of them.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Oct 26 00:30:39 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=30765
Summary: Nightly build of Safari and Chrome 4 remove two
functions registered to window.onload event when
calling removeEventListener to remove the first one of
them.
Product: WebKit
Version: 528+ (Nightly build)
Platform: PC
URL: http://dnf.qq.com/
OS/Version: Windows XP
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: JavaScriptCore
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: hanrui.gao at gmail.com
CC: johnnyding.webkit at gmail.com
Created an attachment (id=41850)
--> (https://bugs.webkit.org/attachment.cgi?id=41850)
Screenshot for your reference.
Other browsers tested:
Nightly build of Safari: Fail
Chrome 4: Fail
Public Released Safari 4: OK
Firefox 3.x: OK
IE 7/8: OK
Chrome 3: OK
What steps will reproduce the problem?
1. Load the url
2. Pay attention to the right area of gray showing "数据载入中..." (The Chinese
means "Data loading...")
3. Nightly build of Safari and Chrome 4 cannot load the content of this area
while Chrome 3 can (as well as other browsers)
What is the expected result?
Nightly build of Safari and Chrome 4 show the content of the gray area as same
as Chrome 3 and other browsers.
What happens instead?
Nightly build of Safari and Chrome 4 cannot load the content in this area.
Please provide any additional information below. Attach a screenshot if
possible.
This page adds two event listener to window.onload, and the first one
("cdn_sendData()" ) removes itself in itself.
But this causes Nightly build of Safari and Chrome 4 to remove the second
function("loadifrs()") registered to window.onload event unexpectedly.
Chrome 3 and public released Safari 4 have not this bug.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list