Closed
Bug 1901077
Opened 1 year ago
Closed 1 year ago
Make GIF decoder yield frame at frame complete rather than next frame start
Categories
(Core :: Graphics: ImageLib, defect)
Core
Graphics: ImageLib
Tracking
()
RESOLVED
FIXED
130 Branch
| Tracking | Status | |
|---|---|---|
| firefox130 | --- | fixed |
People
(Reporter: aosmond, Assigned: aosmond)
Details
Attachments
(1 file)
WebCodecs tests verify that the decoder is able to produce frames as data comes in. They are structured such that only the bare minimum of data is provided, so we don't have the start of the next frame when it expects us to produce the current frame. We actually wait until the next frame starts before notifying the decoder listener about the previous frame, and there isn't much reason to do this. Let's fix that.
| Assignee | ||
Comment 1•1 year ago
|
||
Originally we would yield a new frame when the next frame was available,
or the decoder finished. This is problematic for some WPTs used by
WebCodecs image decoding. There should be no functional difference
besides yielding a new frame slightly earlier.
Pushed by aosmond@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7aa82d756333
Switch GIF decoder to yield new frames at terminating block. r=tnikkel
Comment 3•1 year ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox130:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 130 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•