Make WordPress Core

Opened 5 months ago

Last modified 4 months ago

#61476 new defect (bug)

mediaelement.js fails to rewind audio file when forwarding audio with AirPlay from iPhone to Mac

Reported by: f26d's profile f26d Owned by:
Milestone: Future Release Priority: normal
Severity: minor Version: 6.6
Component: Media Keywords: has-testing-info
Focuses: Cc:

Description

Follow these steps to reproduce:

  • Have an iPhone and a Mac (I'm running iOS 17.5.1 and macOS Sonoma 14.5)
  • Forward audio from your phone to your Mac using AirPlay
  • Have a blog post containing an audio shortcode
  • Open the blog post in Safari on your phone and play the audio. The audio should play on your Mac.
  • When the audio has finished playing, the scrubber bar will try to rewind to the start, but it will get stuck and glitch along the way.

I debugged this problem to understand why it happens. When the audio file has finished playing and the ended event fires, mediaelement.js rewinds the player to time=0. This happens because of the autoRewind option, which is true by default (we don't modify the default). But somehow, the AirPlay connection won't let the audio file rewind, which causes the glitch.

Attachments (1)

RPReplay_Final1718880128.mov (696.8 KB) - added by f26d 5 months ago.
Screencast showcasing the bug

Download all attachments as: .zip

Change History (6)

@f26d
5 months ago

Screencast showcasing the bug

#1 @nightnei
4 months ago

Update for "steps to reproduce"

"Have a blog post containing an audio shortcode" - I could not reproduce it with a random mp3 file, but it looks like it's 100% reproducible with audios from the "Post by Voice" feature.

This ticket was mentioned in Slack in #core-test by ankit-k-gupta. View the logs.


4 months ago

#3 @hardikgohil
4 months ago

  • Keywords has-testing-info added

This ticket was mentioned in Slack in #core-media by antpb. View the logs.


4 months ago

#5 @joedolson
4 months ago

  • Milestone changed from Awaiting Review to Future Release

It's most likely that any solution to this would require an update of the MediaElement.js library, which is currently under discussion in #56320. Can you check whether this is an issue in more recent versions of MediaElement.js, @f26d?

Note: See TracTickets for help on using tickets.