Closed
Bug 726271
Opened 14 years ago
Closed 14 years ago
Motion JPEG should retain previous frame while drawing incoming frame
Categories
(Core :: Graphics: ImageLib, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 625012
People
(Reporter: Dolske, Unassigned)
References
()
Details
Reported from IRC. Loading a progressive JPEG on a current nightly is suboptimal.
After a frame is shown, the image is cleared and then the next frame is drawn (or the image is cleared when the next frame starts?). Essentially, this means that the closer a pixel is to the bottom of the image, the more time it spends being blank.
Chrome seems to do the right thing here. Either it's not doing any incremental display, or it's retaining the previous decoded frame as it displays the next frame.
|
Reporter | |
Comment 1•14 years ago
|
||
Blah. Using the wrong term -- not "progressive jpeg", but rather "motion jpeg".
Summary: Progressive JPEG should retain previous frame while drawing incoming frame → Motion JPEG should retain previous frame while drawing incoming frame
|
|
Reporter | |
Comment 2•14 years ago
|
||
And now I can find bug 625012!
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•