Closed
Bug 18724
Opened 25 years ago
Closed 24 years ago
Progress notifications not hitting!
Categories
(Core :: Networking, defect, P3)
Tracking
()
VERIFIED
FIXED
M17
People
(Reporter: gagan, Assigned: gagan)
Details
(Whiteboard: 2d)
Attachments
(3 files)
2.91 KB,
patch
|
Details | Diff | Splinter Review | |
6.88 KB,
patch
|
Details | Diff | Splinter Review | |
4.83 KB,
patch
|
Details | Diff | Splinter Review |
Updated•25 years ago
|
Target Milestone: M14
Hitting?
Bulk move of all Necko (to be deleted component) bugs to new Networking
component.
Comment 2•25 years ago
|
||
I made a hack that gets progress notifications from httpchannel
to progressmeter. Patch attached.
Comment 3•25 years ago
|
||
law: I am checking in this patch which seems to do the job from HTTP part. Could
you verify that you are indeed getting this information (I am not sure how/where
this would be displayed) Are we planning to display in on the status bar as in
4.x?
Status: NEW → ASSIGNED
Updated•25 years ago
|
Whiteboard: [pdt-]
Comment 5•25 years ago
|
||
Comment 6•25 years ago
|
||
Here is pach #2, this makes also notifications to statusbar:
3k of 10 loaded
Document loaded in 2.77 sec (6k 2.40 kb/sec)
There is some ugly static variables (should be attributes of
nsBrowserAppCore),
also some stuff with frames, should check that if this is frame or not.
Gagan also says that this should live in webshell..
the progress notifications are in a state of big change right now and so I am
pushing this till M18...
Target Milestone: M16 → M18
Comment 10•25 years ago
|
||
Travis made nice job with progress notifications. I moved my progressbar patch
to JS, just like onStatus. I attach new patch, not so ugly hack anymore,
puts simple progressbar working.
Keywords: beta2
Comment 11•25 years ago
|
||
Comment 12•24 years ago
|
||
Per gagan..ok to mark Fixed. Checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•