Error raised when trying to seekTo on Firefox
See original GitHub issueHello, When I try to click on any part of the waveform on firefox, this error is raised :
TypeError: Value being assigned to HTMLMediaElement.currentTime is not a finite floating-point value.
Looking at the sources, it seems that in this function :
this.drawer.on("click", function(e, progress) { setTimeout(function() { console.log(progress); my.seekTo(progress); }, 0); });
the value of progress is Infinity
At this point, I don’t know what to do to solve this, any ideas ?
Issue Analytics
- State:
- Created 6 years ago
- Comments:18 (5 by maintainers)
Top Results From Across the Web
Websites don't load - troubleshoot and fix error messages
The problem only happens with certain websites · Try clearing Firefox's cookies and cache · The website loads but doesn't work properly ·...
Read more >Firefox doesn't recognize if video src gets interrupted
On firefox nothing happened at all. The error is never raised. I tried to work around this a bit and noticed that firefox...
Read more >Firefox Hits Out At Google Chrome's Manifest V3 - Forbes
While Firefox has always been a viable alternative to Chrome, ... The only problem is, some tools are optimized for Chromium-based browsers, ...
Read more >Google Chrome - Wikipedia
It was first released in 2008 for Microsoft Windows, built with free software components from Apple WebKit and Mozilla Firefox. Versions were later...
Read more >Internet Troubleshooting | Spectrum Support
Firewalls: A firewall monitors all network traffic on your computer, so a strict firewall can lead to slow internet speeds. Try restarting your...
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 FreeTop 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
Top GitHub Comments
I’m still experiencing this issue when I remove my work-around. IMO the work-around is still better than crashing the whole script, would a PR be welcome? @katspaugh @thijstriemstra
yep.