MediaError object describes the error in general terms using a numeric
code categorizing the kind of error, and a
message, which provides specific diagnostics about what went wrong.
This interface doesn't inherit any properties.
- A number which represents the general type of error that occurred, as follows:
Name Value Description
The fetching of the associated resource was aborted by the user's request.
Some kind of network error occurred which prevented the media from being successfully fetched, despite having previously been available.
Despite having previously been determined to be usable, an error occurred while trying to decode the media resource, resulting in an error.
The associated resource or media provider object (such as a
MediaStream) has been found to be unsuitable.
DOMStringobject containing a human-readable string which provides specific diagnostic information to help the reader understand the error condition which occurred; specifically, it isn't simply a summary of what the error code means, but actual diagnostic information to help in understanding what exactly went wrong. This text and its format is not defined by the specification and will vary from one user agent to another. If no diagnostics are available, or no explanation can be provided, this value is an empty string (
This interface doesn't implement or inherit any methods, and has none of its own.
|HTML Living Standard
The definition of 'MediaError' in that specification.
We're converting our compatibility data into a machine-readable JSON format. This compatibility table still uses the old format, because we haven't yet converted the data it contains. Find out how you can help!
|Feature||Chrome||Edge||Firefox (Gecko)||Internet Explorer||Opera||Safari|
|Basic support||(Yes)||(Yes)||3.5 (1.9.1)||9||?||?|
|Feature||Android Webview||Chrome for Android||Edge||Firefox Mobile (Gecko)||Firefox OS (Gecko)||IE Mobile||Opera Mobile||Safari Mobile|
 While the
message property was introduced in Firefox 51, it was only included in nightly builds since it was not part of the specification at that time. As of Firefox 52, it's now available in all builds, including release, since it's now part of the HTML DOM specification.