Clean up WebMediaPlayer -> HTMLMediaElement error reporting |
|||||||
Issue descriptionFrom bug 472253 , this bug tracks follow-up work to further improve the spec and impl for HTMLMediaElement exposure of a meaningful error message to web apps: 1. Split NetworkState*Error from WebMediaPlayer::NetworkState and instead have a dedicated error callback. (Decoding errors don't necessarily impact the network fetch at all.) 2. Add a message attribute to MediaError, so that web apps can also learn about these errors from the wild.
,
Apr 6 2016
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 14 2016
This issue has been moved once and is lower than Pri-1. Removing the milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 29 2017
Follow-up in OP item #2 was fixed by MediaError.message: bug 601086 and bug 710617 in M59. Renaming this bug to track improving code path between WebMediaPlayer and HTMLMediaElement for notifying errors (OP item #1).
,
Oct 1
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 21
The remaining work (item #1 in OP) is still pending. Seems unlikely to get fixed in near term and is low priority. CLosing. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by wolenetz@chromium.org
, Apr 6 2016