WebM buffered range parser should be aware of sync points and adjust reported ranges

RESOLVED FIXED in mozilla34

Status

()

defect
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: kinetik, Assigned: kinetik)

Tracking

Trunk
mozilla34
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

This affects the start of reported ranges.  If the buffered start point is not a sync point (i.e. key frame), the reported buffered range should be adjusted forward to the nearest sync point as that's the nearest possible place that decoding can resume from without fetching additional data.
Bug 1050083 gets this part way by recording the sync point of every time/data offset record.
Bug 1044498 completes this work.
Depends on: 1044498
Depends on: 1050083
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
You need to log in before you can comment on or make changes to this bug.