Closed
Bug 1448181
Opened 7 years ago
Closed 6 years ago
media readyState behavior changed
Categories
(Core :: Audio/Video: Playback, defect, P2)
Tracking
()
RESOLVED
DUPLICATE
of bug 1457661
People
(Reporter: ddrogahn, Assigned: bryce)
References
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180322100349
Steps to reproduce:
In current versions: a force-preloaded media file does not go past readyState 3 HAVE_FUTURE_DATA.
Did work in previous versions, and does work in other browsers.
https://jsfiddle.net/ddrogahn/sdjadd2s/
Force-Preload: fetch(url), URL.createObjectURL(response.blob), audio.src = objUrl, wait for readyState or event
Actual results:
oncanplay event
readyState = 3
59.0 and 59.0.1 and Nightly 61.0a1 (2018-03-22) have this behavior
Expected results:
oncanplay event
oncanplaythrough event
readyState = 4
Previous FF version: v58.0.2 is OK
Other browsers: Edge 16, Chrome 65.0.3325.181 are OK.
Comment 1•7 years ago
|
||
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=772fef647fd7750f8c87dfd4f55bbd85046a555a&tochange=821560cd716d50fbb0c49d0170bd351255e55bc3
Regressed by: Bug 1423465
@:jw_wang,
Your bunch of patch seems to cause the regression, can you look into this?
Blocks: 1423465
Status: UNCONFIRMED → NEW
status-firefox59:
--- → wontfix
status-firefox60:
--- → fix-optional
status-firefox61:
--- → affected
Component: Untriaged → Audio/Video: Playback
Ever confirmed: true
Flags: needinfo?(suro001)
Keywords: regression
Product: Firefox → Core
Updated•7 years ago
|
Flags: needinfo?(suro001)
Comment 2•7 years ago
|
||
This also affects video playback. See the console output here - https://jsfiddle.net/h21qrzno/
Comment 3•7 years ago
|
||
Any updates on this? This is definitely breaking a few video implementations I've seen.
Updated•6 years ago
|
status-firefox62:
--- → fix-optional
status-firefox-esr52:
--- → unaffected
status-firefox-esr60:
--- → wontfix
Version: 61 Branch → 59 Branch
Comment 4•6 years ago
|
||
Gerald, do you have cycles to look at this by chance?
Flags: needinfo?(gsquelart)
JW is gone, and officially I'm not in media anymore, all my cycles are spent in layout.
Jean-Yves, you're probably the best person left! Please contact me if you'd like to discuss.
Flags: needinfo?(gsquelart) → needinfo?(jyavenard)
Comment 6•6 years ago
|
||
:bryce, is this something you could take?
Flags: needinfo?(jyavenard) → needinfo?(bvandyk)
Comment 7•6 years ago
|
||
Seems like a fairly high-impact regression that already made it to release. Making it a high P2 but feel free to adjust.
Rank: 12
Priority: -- → P2
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → bvandyk
Flags: needinfo?(bvandyk)
Assignee | ||
Comment 8•6 years ago
|
||
Looks like this is a dupe of bug 1457661. Have verified the fix there has fixed this in all versions where the fix was applied. 1457661 landed test coverage, but I'm going to take a look at if there's anything extra we should be covering that's different for this case. If so, I will raise a follow up bug for further tests.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 9•6 years ago
|
||
Following up from comment 8: I think the already landed test provides sufficient coverage of the underlying issue for both bugs.
You need to log in
before you can comment on or make changes to this bug.
Description
•