Closed Bug 18724 Opened 25 years ago Closed 24 years ago

Progress notifications not hitting!

Categories

(Core :: Networking, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: gagan, Assigned: gagan)

Details

(Whiteboard: 2d)

Attachments

(3 files)

Target Milestone: M14
Hitting?
Bulk move of all Necko (to be deleted component) bugs to new Networking component.
Keywords: beta1
I made a hack that gets progress notifications from httpchannel to progressmeter. Patch attached.
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
Whiteboard: [pdt-]
Target Milestone: M14 → M15
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..
Keywords: beta2
Moving what's not done for M15 to M16.
Target Milestone: M15 → M16
Keywords: beta1
Whiteboard: [pdt-] → 2d
the progress notifications are in a state of big change right now and so I am pushing this till M18...
Target Milestone: M16 → M18
Moving beta2 bugs out of M18.
Target Milestone: M18 → M17
Keywords: nsbeta2
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
Per gagan..ok to mark Fixed. Checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
verif: NT 2000053108
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: