Media Element Binding for set currentTime is unreliable
See original GitHub issueDescribe the bug
The Media Element Binding for setting bind:currentTime={time}
is unreliable when setting single times. For example a list of video position index markers. Clicking on an index, which sets the currentTime, doesn’t always set the video position. Where as if I set currentTime via the DOM method then it does work every time.
To Reproduce Here’s a couple of examples the issue: https://svelte.dev/repl/3470317362744bf296ae78b688445448?version=3.9.2 https://svelte.dev/repl/17fecf5e4b5449a79f7eda6abc480f19?version=3.9.2
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
How to bind Slider position to Current ElementMedia time ...
I would like to retrive the current elapse time of the video then set the Maxvalue and Current value of my seek slider...
Read more >Cannot use setCurrentTime() in Chrome with mediaelement.js
MEJS can't set the time until the media is loaded. Use the "loadeddata" event. $('#video').bind('loadeddata', function(e) { if (player.
Read more >66631 - Video frame displayed does not match currentTime
If video.currentTime doesn't return accurate results, then said subtitle elements WILL end up displaying outside their allotted time. This can ...
Read more >Bindings / Media elements • Svelte Tutorial
currentTime — the current point in the video, in seconds; playbackRate — how fast to play the video, where 1 is 'normal'; paused...
Read more >HTMLMediaElement.currentTime - Web APIs | MDN
Setting currentTime to a new value seeks the media to the given time, if the media is available. For media without a known...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m also having this issue on Firefox 80.0.1 and Svelte v3.24.0, macOS 10.15.6. Works fine in Chrome.
Released 3.10.1 with the fix — thanks!