You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
just ran into another bug? seems that the media-time-range scrub and skimming is broken with the latest iOS update? Running iOS 17.5. It looks like it skims and updates, but one play it reverts back to the original playhead position?
Seems to be only an issue before the video starts play. And leaves the UI timecode vulnerable to being completely out of sync and just wrong
Some further research and testing from my end, it seems to happen most frequently when the video hasn't started loading for some reason.
and to confirm, you weren't seeing this in iOS previously??
correct. in prior iOS versions this was not an issue. my guess is some sort of bug between loading the video player and the browser not letting it happen?
related #910
this fixes an issue where when you seek before the video is loaded we
don't set the video.currentTime.
it's fine to set the currentTime anytime. it doesn't throw for a valid
number value.
but users have to set the `defaultduration` in some cases. not sure with
iOS and native HLS.
This has at least been partly fixed. We've successfully tested it on desktop and iOS 17 physical device.
On iOS 18 via Browserstack it was not working.
just ran into another bug? seems that the media-time-range scrub and skimming is broken with the latest iOS update? Running iOS 17.5. It looks like it skims and updates, but one play it reverts back to the original playhead position?
Seems to be only an issue before the video starts play. And leaves the UI timecode vulnerable to being completely out of sync and just wrong
Some further research and testing from my end, it seems to happen most frequently when the video hasn't started loading for some reason.
You can see it happen even on desktop in the media-chrome examples:
https://media-chrome.mux.dev/examples/vanilla/state-change-events-demo.html
The text was updated successfully, but these errors were encountered: