Closed Bug 553479 Opened 14 years ago Closed 14 years ago

Download progress XBL binding doesn't support unknown sizes

Categories

(Toolkit :: Add-ons Manager, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla1.9.3a5

People

(Reporter: Unfocused, Assigned: Unfocused)

References

()

Details

(Whiteboard: [rewrite][AOMTestday])

Download progress XBL binding doesn't support unknown sizes. When a file-size is unknown, the progressmeter should be set to undetermined mode.
Is that a general widget issue?
(In reply to comment #1)
> Is that a general widget issue?

No, specific to the custom binding (download-progress in extensions.xml) that shows the progress bar and status text.
Also, should be able to automate testing on this.
Flags: in-testsuite?
Flags: in-litmus-
Seems this was fixed awhile ago.

http://hg.mozilla.org/projects/addonsmgr/rev/57f34bdf1358
Whiteboard: [rewrite] → [rewrite][fixed-in-addonsmgr]
Assignee: nobody → bmcbride
Landed on trunk as a part of bug 554007
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [rewrite][fixed-in-addonsmgr] → [rewrite]
Target Milestone: --- → mozilla1.9.3a5
Any chance to get this manually tested for verification? We always send the extension size on AMO, right?
(In reply to comment #6)
We always send the extension size on AMO, right?

As far as I know, yea. To test, you need a server that won't send the size in the HTTP headers (also doable via a server-side script).
General implementation works, even the binding is broken on OS X. See bug 616643.

Talked with Blair on IRC and as it turns out a manual test would be necessary because there seems to be no way to let httpd server content without a content length. Dave, or would that be possible?

Verified fixed with Mozilla/5.0 (Windows NT 5.1; rv:2.0b8pre) Gecko/20101203 Firefox/4.0b8pre by testing: http://mozilla.hskupin.info/aom/undetermined/
Status: RESOLVED → VERIFIED
Depends on: 616643
Flags: in-litmus- → in-litmus?
Whiteboard: [rewrite] → [rewrite][AOMTestday]
Version: unspecified → Trunk
(In reply to comment #8)
> General implementation works, even the binding is broken on OS X. See bug
> 616643.
> 
> Talked with Blair on IRC and as it turns out a manual test would be necessary
> because there seems to be no way to let httpd server content without a content
> length. Dave, or would that be possible?

Should be possible, a server side script like php ought to be about to output content with no content length header.
(In reply to comment #9)
> Should be possible, a server side script like php ought to be about to output
> content with no content length header.

Yea, that's what he did (the the URL in comment 8) - when he says "httpd" there, he really means httpd.js in mochitest (which I know very little about).
Ok, so testing the undetermined mode should be possible with httpd.js. As given by Jeff we would have to do the following:

but if you *only* want to disable content-length, you should seizePower() and write exactly the bytes you want, so as not to rely on the mechanics of content-length provision
Would be great to get an automated test for it. In the meantime we will have a manual one. The extension provided in the url will show an undetermined progress meter.
As addition, for the Litmus test we have to check that the undetermined progress meter is used and the start and end caps are displayed correctly.
Talked with Blair on IRC and we agreed on that it is not worth a test. Everything here is nearly CSS and it will take us a lot of time to create a test in either case, manual or automated.
Flags: in-testsuite?
Flags: in-testsuite-
Flags: in-litmus?
Flags: in-litmus-
You need to log in before you can comment on or make changes to this bug.