Bug 3791

Summary: Events created in popups fail to fire after popup closed
Product: WebKit Reporter: Christopher Lord <christopherlord>
Component: JavaScriptCoreAssignee: Maciej Stachowiak <mjs>
Status: RESOLVED FIXED    
Severity: Normal CC: ian, list
Priority: P2 Keywords: HasReduction
Version: 412   
Hardware: Mac   
OS: OS X 10.4   
URL: http://www.clawbox.com/misc/testcase.html
Attachments:
Description Flags
demonstrates the problem none

Christopher Lord
Reported 2005-07-01 09:51:53 PDT
An event attached via javascript to a page object inside a popup only fires so long as the popup remains open. Other data and objects created in this manner work correctly. URL points to a test case which demonstrates. Reproduce: Click 'Add Item Via Popup', add some data (to identify your new item), and click the button. The originating form gains a new button and your string. Switch from popup (leave open) open and click remove. The row should go away. Now repeat, but close popup before clicking remove. Safari will no longer remove the row, but no error is reported in js console. Test case works in Firefox for Mac.
Attachments
demonstrates the problem (1.59 KB, text/html)
2005-07-01 09:53 PDT, Christopher Lord 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Christopher Lord
Comment 1 2005-07-01 09:53:18 PDT
Created attachment 2730 [details] demonstrates the problem
Joost de Valk (AlthA)
Comment 2 2005-07-01 11:12:26 PDT
Confirmed, very good testcase!
Alexey Proskuryakov
Comment 3 2006-08-28 22:12:50 PDT
See also: bug 7783.
Olaf Gleba
Comment 4 2006-10-05 03:14:41 PDT
Thank you for finding out. I was working on that. This bug is a killer in deed. Hopefully this will be fixed as soon as possible, cause this function is in use on a regular bases.
Olaf Gleba
Comment 5 2007-03-13 01:29:17 PDT
As there is no change in the status since the bug reported, i wonder if there is any chance to fix this bug within a reasonably period? This bug simply means, for example, our Web 2.0 CMS is dead on Safari. Would be a shame.
Khoo Yit Phang
Comment 6 2008-02-12 17:07:12 PST
Just browsing around, but it seems that this bug has been fixed? The test page seems to work fine with the nightly revision 30153.
David Kilzer (:ddkilzer)
Comment 7 2008-02-22 16:02:12 PST
This is fixed (per reduction) as of a local debug build of WebKit r30458.
Note You need to log in before you can comment on or make changes to this bug.