Open
Bug 395634
Opened 17 years ago
Updated 2 years ago
busy cursor is permanent after page closes itself from onload
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
NEW
People
(Reporter: ajschult784, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file)
|
323 bytes,
text/html
|
Details |
With a current trunk build, if a page closes its tab from its onload handler, the cursor stays in the busy state. DocShell receives STATE_STOP events, but it only resets the cursor if it receives STATE_STOP | STATE_IS_NETWORK (and it does not receive that).
Steps to reproduce:
1. load the attached testcase (warning: crashes SeaMonkey builds before 9/10)
2. click the link
[page opens, closes itself from onload]
3. hover over any chrome
==> busy cursor
|
||
Comment 1•17 years ago
|
||
This worksforme with current trunk builds, both seamonkey and firefox.
|
Reporter | |
Comment 2•17 years ago
|
||
hmm. I do see it with both seamonkey and firefox.
|
|
||
Comment 3•17 years ago
|
||
In a debug build too?
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•