Closed Bug 797183 Opened 12 years ago Closed 12 years ago

On XP stub install progress bar starts at 100% and download progress bar doesn't go to 100%

Categories

(Firefox :: Installer, defect)

Product:
Firefox
Component:
Installer
Version:
17 Branch
Platform:
All
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: jsmith, Assigned: robert.strong.bugs)

References

Details

(Keywords: polish, Whiteboard: [stub=]) 

When I install Firefox on Windows XP, the use of progress bars to demonstrate progress of download and install just feels a bit awkward and confusing. Some issues I'm seeing include:

- Right after starting the download phase, I'm seeing a part of installing phase progress bar already filled out. Then, later after download is complete, that disappears, and goes into the "discovery" phase of trying to figure out the progress to install. Right at the beginning of the download phase, we haven't installed anything, right? So why is anything being shown.
- When I finish the download phase, part of progress bar remains rendered in the download progress bar, even though downloading is entirely done. Shouldn't we give a clear indication that the download is complete, rather than leaving a progress bar behind?
Blocks: StubInstaller
Assignee: nobody → robert.bugzilla
Note - this is an OS-specific bug. This problem reproduces on Win XP, but will not reproduce on Win 7.
Summary: The sense of "progress" when installing Firefox with the stub installer seems confusing - progress bars follow in a strange, but not connected order → On XP stub install progress bar starts at 100% and download progress bar doesn't go to 100%
Keywords: polish
Whiteboard: [stub=]
It looks like this also got fixed by the patch in bug 800112.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
And marking as verified for 10/12 nightly build.
Status: RESOLVED → VERIFIED
I had my fingers crossed that the changes made in bug 800112 would fix this. :)
Depends on: 800112
You need to log in before you can comment on or make changes to this bug.