Error event for audio element not dispatched
Reported by
destine....@gmail.com,
Aug 29
|
|||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36
Steps to reproduce the problem:
1. Create Audio element with a valid playable audio src
2. Register a callback to the error event of the element => element.addEventListener("error", callback);
3. invoke element.play() without user interaction.
What is the expected behavior?
Due to autoplay policy the playback is not started.
Callback for the error event is invoked and the promise returned by the play() method is rejected.
What went wrong?
The playback is indeed not started BUT
the error event is never trigered and therefore the callback is never invoked
Did this work before? N/A
Chrome version: 67.0.3396.87 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
The promise is rejected as expected.
,
Aug 30
Tested on Chrome 68.0.3440.106 same issue.
,
Aug 30
,
Aug 31
destine.loic@ - Thanks for filing the issue...!! Could you please provide a sample test file/url to test the issue from TE-end. This will help us in triaging the issue further. Thanks...!!
,
Aug 31
Of course, Here a simple exemple : https://codepen.io/kezine/pen/QVddoY?editors=1010
,
Aug 31
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 5
Tested the issue on Win-7 and Win-10 using chrome latest stable #56.0.2924.87 and latest canary #71.0.3542.0 and M-60 as per comment #5. Attached a screen shots for reference. destine.loic@ - Could you please check the attached screen shots and please let us know the issue if present in M-60 or M-69. An expected/actual screen shot from your end will be really helpful in further triaging of the issue. Thanks...!!
,
Sep 5
I've adapted a little bit the test but the logic is the same. Tested on W7 M-67 And Win-10 with the latest M-69. For clarification, the actual console output is : ***** TEST A **** (A) Mehhh, cannot play this ... (As expected and normal) => NotAllowedError: play() failed because the user didn't interact with the document first. ***** TEST B **** (B) Mehhh, cannot play this ... (As expected and normal) => NotAllowedError: play() failed because the user didn't interact with the document first. (B) Is executed when the problem preventing playback is not exclusively the "NotAllowedError" or not this error at all. The expected output without the supposed bug : ***** TEST A **** (A) Mehhh, cannot play this ... (As expected and normal) => NotAllowedError: play() failed because the user didn't interact with the document first. (A) Should be trigered ... but isn't ***** TEST B **** (B) Mehhh, cannot play this ... (As expected and normal) => NotAllowedError: play() failed because the user didn't interact with the document first. (B) Is executed when the problem preventing playback is not exclusively the "NotAllowedError" or not this error at all. I've tested on M-60(60.0.3112.78) but the bug is not occuring since the autoplay policy on audio element for this version does not prevent autoplay without user interaction. (screenshot attached)
,
Sep 5
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 5
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by viswa.karala@chromium.org
, Aug 29