Open
Bug 832729
Opened 12 years ago
Updated 2 years ago
tabbrowser progress listener no longer fires STATE_STOP on async requests
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: sparky, Unassigned)
Details
Attachments
(1 file)
438 bytes,
text/html
|
Details |
Previous to Firefox 17, loading content outside of the main document load would trigger a series of onStatusChange events, followed by an onStateChange STATE_STOP|STATE_IS_REQUEST event. The STATE_STOP event appears to no longer be triggered (or is filtered out).
This was first reported to me by an Status4Evar user on Firefox 17, and I can still reproduce it on the current trunk.
http://forums.mozillazine.org/viewtopic.php?p=12500891#p12500891
onStatusChange log:
aWebProgress.isLoadingDocument, aRequest.URI.spec, aRequest.status, aStatus.toString(16), aMessage
onStateChange log:
aWebProgress.isLoadingDocument, aRequest.URI.spec, aRequest.status, aStatus.toString(16), aStateFlags.toString(16)
Firefox 16:
true, file:///home/sparky/Desktop/test.html, 0, 0, f0001
false, file:///home/sparky/Desktop/test.html, 0, 0, c0010
null, null, null, 0, Looking up upload.wikimedia.org…
null, null, null, 0, Waiting for upload.wikimedia.org…
null, null, null, 0, Transferring data from upload.wikimedia.org…
false, null, 0, 0, 10010
Firefox 21:
true, file:///home/sparky/Desktop/test.html, 0, 0, f0001
false, file:///home/sparky/Desktop/test.html, 0, 0, c0010
null, null, null, 0, Looking up upload.wikimedia.org…
null, null, null, 0, Transferring data from upload.wikimedia.org…
Reporter | ||
Comment 1•12 years ago
|
||
Reporter | ||
Updated•12 years ago
|
Attachment #704306 -
Attachment mime type: text/plain → text/html
![]() |
||
Updated•12 years ago
|
Component: General → Networking: HTTP
Comment 2•12 years ago
|
||
STATE_STOP is nsIWebProgressListener.idl which belongs to doc navigation.
Component: Networking: HTTP → Document Navigation
Comment 3•12 years ago
|
||
Anybody wants to test this problem with XUL <browser/> instead of <tabbrowser/> ? That will tell us docshell's (or necko's) bugs from tabbrowser's (or toolkit's) bugs.
This is now working again. It looks like it was fixed by something in this range:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=161a347bda5b&tochange=aceeea086ccb
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•