Log contains misleading stalled events
Created by: davemevans
Environment
-
The MPD passes the DASH-IF Conformance Tool on http://dashif.org/conformance.html -
The stream has correct Access-Control-Allow-Origin headers (CORS) -
There are no network errors such as 404s in the browser console when trying to play the stream -
The issue observed is not mentioned on https://github.com/Dash-Industry-Forum/dash.js/wiki/FAQ -
The issue occurs in the latest reference client on http://reference.dashif.org/dash.js/ and not just on my page
- Link to playable MPD file: Any MPD with media segments longer than 3 seconds eg http://rdmedia.bbc.co.uk/dash/ondemand/testcard/1/client_manifest-events.mpd
- Dash.js version: nightly
- Browser name/version: Chrome 66
- OS name/version: Win7
Steps to reproduce
- Load http://rdmedia.bbc.co.uk/dash/ondemand/testcard/1/client_manifest-events.mpd
- Wait until all media buffers have reached their target (ie 60s)
- Observe player logs in dev console
Observed behaviour
Media element stalled events are misleading when using MSE. In this example, Chrome will emit stalled events whenever media has not been appended for more than three seconds. The player listens for these and logs Native video element event: stalled.
I think this log message is misleading since (to me) it appears to imply that the media element's buffer is starved when in fact it is unrelated. I think there is potential for new users to be confused by this and therefore I wonder if the message should either have its priority decreased (so it doesn't show up in default-level logging sessions), or removed entirely.
Note that Chrome will deprecate emitting this event from v69: https://www.chromestatus.com/feature/6338037575319552