mirror of
https://github.com/koel/koel.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #532] Music stops after first song on Firefox > v51 #376
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#376
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @X-Ryl669 on GitHub (Feb 5, 2017).
Original GitHub issue: https://github.com/koel/koel/issues/532
With latest firefox, when playing multiple songs in the queue, the first song plays fine but any other later song fails to play. This also happens with your demo.
It works with webkit latest version and firefox < 49.
There's no message in the javascript console, no exception whatsoever, the interface just looks like fine (the time is increasing etc...) but no sound is produced and the speaker icon is not overlaid on the browser's tab (as when audio is running).
Demo on player.js runs fine.
@Diagamma commented on GitHub (Feb 6, 2017):
I have this issue too. By the way, it works perfectly with Firefox Developer Edition (v53.0a2).
@X-Ryl669 commented on GitHub (Feb 6, 2017):
Is there anything in the Firefox's changelog that could explain they corrected the bug ?
I've tried to report the bug on Mozilla, but it's almost impossible to find out if it's already there, or if it's corrected already, etc...
I just want to make sure it's fixed in the upcoming version 52 or 53 or if it's a side effect of the multi-process change they added (and in that case, figure out if the usage pattern of player.js in Koel is wrong)
@phanan commented on GitHub (Feb 8, 2017):
But Koel doesn't use player.js. I'd suspect something went wrong with
document.querySelector('.plyr').addEventListener('ended'inplayback.js, or the preload functionality. Will take a look when I have some time – sorry, I'm really busy recently.@X-Ryl669 commented on GitHub (Feb 14, 2017):
Tested v52beta6 and it's working. I'll close this bug when official 52 is out and the issue does not happen.
@X-Ryl669 commented on GitHub (Mar 8, 2017):
Official version 52 is out, and it works. Thanks.