Audio Element - playing event is not triggered after stalled

Won’t fix Issue #11444072

Details

Author
Hao B.
Created
Mar 29, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Hi,

We are experiencing an issue with Edge after audio stalls and here’s the jsfiddle to reproduce the issue: https://jsfiddle.net/mnbukcuq/

Steps:

  1. Start playback.
  2. Before the track is prefetched, turn off the network/throttle the network to make the audio stalls.
  3. Turn network back online/remove throttling and let the playback resumes.

Expected behavior: when audio resumes, it should fire a play event.
Actual behavior: play event is never fired.

Previously, we also reported a similar issue: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/10437243/ for play is not triggered after seeking. This issue can also be reproduced with the above jsfiddle.

Thanks!

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Nishant N.”

    • Can we have an update?
      This is important for us so we can handle the resuming from stall properly.

      Thanks!

    • Microsoft Edge Team

      Changed Assigned To to “Sudhakar P.”

      Changed Assigned To from “Sudhakar P.” to “Matthew H.”

      Changed Status to “Confirmed”

      Changed Title from “Audio MSE - playing event is not triggered after stalled” to “Audio Element - playing event is not triggered after stalled”

    • Hi, sorry for the expired mp3. I have updated the fiddle with a new mp3 and we are experiencing a slightly different experience now: http://jsfiddle.net/3b9Lk1wu/5/

      Steps:

      1. Start playback.
      2. Before the track is prefetched, turn off the network/throttle the network to make the audio stalls.
      3. Turn network back online/remove throttling and let the playback resumes.

      Expected behavior: Audio resumes and it should fire a play event.
      Actual behavior: error code 3 emits when audio runs out of audio (waiting) and play event is never fired, and audio never resumes even after network reconnect.

      Thanks,
      Evan

    • Bump.

      Can we have an update?
      With this issue, customer won’t be able to continue progressive track playback if playback stalls due to network offline. Given the bad customer experience, can you take a look at the issue?

      Thanks,
      Hao

    • Microsoft Edge Team

      Changed Status from “Confirmed” to “Won’t fix”

    • Thanks Matthew for the update. Can you provide any rationale why Edge team ‘Won’t fix’ this issue? Do you have any suggestions we can depend on to decide playback resumes?
      This issue happens for both progressive and adaptive tracks.

      Without the ‘playing’ event emitted properly, we can hardly know when the audio playback resumes from stall, and we cannot take effective action to provide better playback experience to customer.

      Looking forward to hearing from the team.

    • Hello,

      Thank you for providing this information about the issue. This is not a regression, and the MF HTTP bytestream errors out if the network is removed, so it won’t get to the point where we could fire the playing event again anyway. Currently, we do not plan to release a fix for this problem. We are considering a solution for a future build.

      Best Wishes,
      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in