Open
Bug 941414
Opened 12 years ago
Updated 3 years ago
onLocationChange handler not firing
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: serge, Unassigned)
Details
Attachments
(1 file)
|
3.03 KB,
application/zip
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.62 Safari/537.36
Steps to reproduce:
I create several browser elements, and call loadURIWithFlags on them. I add a progress listener to handle onLocationChange().
Attached is minimal xulrunner 25.0 app that shows the breaking behavior.
Here's a related stackoverflow question:
http://stackoverflow.com/questions/20107546/firefox-onlocationchange-not-always-called
Actual results:
I expect the onLocationChange handler to be called at least once per created browser element.
Expected results:
For the third url in the example app, the location change handler does not fire. Interestingly, if lines 50 and 51 are wrapped in a setTimeout(..., 5000), the app works as expected.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•