Closed
Bug 1165145
Opened 10 years ago
Closed 10 years ago
Incorrect MediaSource buffered range being reported in ended mode.
Categories
(Core :: Audio/Video, defect)
Core
Audio/Video
Tracking
()
RESOLVED
FIXED
mozilla41
Tracking | Status | |
---|---|---|
firefox41 | --- | fixed |
People
(Reporter: jya, Assigned: jya)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
1.31 KB,
patch
|
karlt
:
review+
|
Details | Diff | Splinter Review |
1.22 KB,
patch
|
karlt
:
review+
|
Details | Diff | Splinter Review |
1.11 KB,
patch
|
karlt
:
review+
|
Details | Diff | Splinter Review |
The MediaSourceReader::GetBuffered() when in ended mode adjust the buffered range so they all end at the same level as the highest end time across source buffer.
This is wrong.
Only a sourcebuffer is to perform such alignment and across the trackbuffers.
(http://w3c.github.io/media-source/index.html#widl-SourceBuffer-buffered)
This cause webref mediasource-buffered.html to fail.
Assignee | ||
Comment 1•10 years ago
|
||
We could report time ranges such as [-1 0] as GetEndTime on an empty TimeRanges return -1
Attachment #8606083 -
Flags: review?(karlt)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → jyavenard
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•10 years ago
|
||
Take "If readyState is ended, then set the end time on the last range in source ranges to highest end time." literally. That is is there s no last range, there s nothing to set.
Attachment #8606085 -
Flags: review?(karlt)
Assignee | ||
Comment 4•10 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=7dd9121994e1
got a previous green try, but made some changes up the chain so redoing them just in case.
Updated•10 years ago
|
Attachment #8606085 -
Flags: review?(karlt) → review+
Updated•10 years ago
|
Attachment #8606086 -
Flags: review?(karlt) → review+
Comment 5•10 years ago
|
||
Comment on attachment 8606083 [details] [diff] [review]
Part1. Never reports negative time ranges with MSE
I had assumed from the commit message that this was meant to remove an existing negative time range, and so it took me a while to work out that this is to prevent adding a (-1,0) time range here because TimeRanges::GetEndTime() returns -1 when there are no ranges, while TrackBuffer::Buffered() returns 0.
Can you change the comment to say "don't add a negative time range to empty buffered ranges" or similar, please?
An alternative fix, possibly making the code easier to follow would be to make Buffered() return -1, like GetEndTime(). However, I guess this is being rewritten in bug 1163445 anyway.
Attachment #8606083 -
Flags: review?(karlt) → review+
Comment 7•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/4b24663ec60e
https://hg.mozilla.org/mozilla-central/rev/3017514d76f3
https://hg.mozilla.org/mozilla-central/rev/bb3eb37c2e2b
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla41
You need to log in
before you can comment on or make changes to this bug.
Description
•