Clarify the difference between the chunks that SourceBufferIterator and Decoder tracks and SourceBuffer's internal chunks

NEW
Unassigned

Status

()

Core
ImageLib
P3
normal
2 years ago
10 months ago

People

(Reporter: seth, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [gfx-noted])

(Reporter)

Description

2 years ago
SourceBuffer has chunks internally; these are just the buffers that incoming data is written into. Decoder has a notion of "chunks" as well, for telemetry purposes: these are how many pieces the image data it's decoding were delivered in, which in modern times corresponds to how many times SourceBufferIterator::AdvanceOrScheduleResume() as called. To make things even more confusing, post bug 1285867 we are now tracking that kind of chunk on SourceBufferIterator!

Let's rename one of these two things, because they're not quite the same, but they *are* similar enough to be confusing.
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.