NotSupportedError: The media resource indicated by the src attribute or assigned media provider object was not suitable
Categories
(Core :: Audio/Video: Playback, defect, P5)
Tracking
()
People
(Reporter: alex.svetos, Unassigned)
References
()
Details
(Keywords: parity-chrome)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0
Steps to reproduce:
- Open https://www.member.russianaccelerator.com/pron4-2/
- Try to read the first audio
Actual results:
Audio is not read, in console I get
Uncaught (in promise) DOMException: The media resource indicated by the src attribute or assigned media provider object was not suitable.
Expected results:
Should have read the audio file tagged <audio> in the html.
|
Reporter | |
Comment 1•6 years ago
|
||
(Running on linux Mint 20)
I tried on a an empty profile in order to have zero extension loaded and I get the same error.
I don't think the audio file are corrupted since the page works fine with chrome.
|
||
Comment 2•6 years ago
•
|
||
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0
20200708170202
(In reply to alex.svetos from comment #0)
Uncaught (in promise) DOMException: The media resource indicated by the src attribute or assigned media provider object was not suitable.
That's at line 38 of https://www.member.russianaccelerator.com/wp-content/plugins/lbg-audio1-html5/audio1_html5/js/audio1_html5.js?ver=5.3.4
The file plays when standalone.
https://ram-s3bubble-pronunciation.s3.amazonaws.com/u4l2/4u2l-a1.mp3
For all MP3 requests on that page, the Network monitor shows Type: x-wav but the details pane shows Content-Type: audio/mpeg
|
|
Reporter | |
Comment 3•6 years ago
|
||
Okay so it's the website that has coding mistakes, ok. thx
|
||
Updated•6 years ago
|
Description
•