Closed Bug 600048 Opened 14 years ago Closed 14 years ago

Use CSS transitions on progress bar states

Categories

(Firefox :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: Margaret, Assigned: Margaret)

References

Details

(Keywords: polish)

Movement from one progress state to the next is choppy, so we should use CSS transitions to create a smoother experience.
See also bug 551433. Using CSS transition for the animation might be tricky. The progress chunk width is set using the flex attribute by C++ code (nsProgressMeterFrame.cpp) based on the XUL value attribute. So there's not much CSS involved.
(In reply to comment #1) > Using CSS transition for the animation might be tricky. The progress chunk > width is set using the flex attribute by C++ code (nsProgressMeterFrame.cpp) > based on the XUL value attribute. So there's not much CSS involved. Hmm, you're right. I think we thought we could use CSS because we are using CSS to style the appearance of the progressmeter. It seems like bug 551433 addresses the problem we're having with the progress lines, so maybe this bug is a dupe. Is there any reason why work on that stopped?
(In reply to comment #2) > Is there any reason why work on that stopped? Other than lack of time, no. Feel free to pick it up if you get to it sooner than I do.
Given the issues encountered in bug 602126, I feel like using CSS transitions for the progress bars states isn't going to be a solution.
Bug 602964 makes this invalid.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.