-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Media Element Binding for set currentTime is unreliable #3524
Comments
Awesome thanks @Rich-Harris - what is the release cycle for this as I'm "newish" to your PR -> master process. So I know when to upgrade my project and then I can feedback on the work am doing with this. |
Released 3.10.1 with the fix — thanks! |
I've downloaded the above example app from the REPL and built it locally with Svelte v3.12.0 and the issue seems to be resolved on Firefox and Chrome (latest builds, Windows 10). |
I'm also having this issue on Firefox 80.0.1 and Svelte v3.24.0, macOS 10.15.6. Works fine in Chrome. |
I'm having this issue in I find that adding
|
It looks like this issue still hasn't been fixed correctly unfortunately. |
I'm still seeing this issue in Firefox 119.0 on macOS Sonoma. The workaround suggested by @quantumwebco worked for me: tick().then(() => currentTime = newTime); |
https://linear.app/beyondwords/issue/S-3758/seeking-is-not-working-well-in-firefox Caused by a Svelte bug: - sveltejs/svelte#6955 - sveltejs/svelte#3524 Fixed using the technique suggested here: sveltejs/svelte#3524 (comment)
Describe 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
The text was updated successfully, but these errors were encountered: