mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #536] Client notices when internet connection goes out and acts accordingly. #379
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#379
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 @itsgreggreg on GitHub (Feb 8, 2017).
Original GitHub issue: https://github.com/koel/koel/issues/536
Chrome, at tag v3.5.4
Right now when I'm offline and try to play a song or hit next Koel zooms through the rest of the playlist generating plays, updating the list of recently played song and loosing my place in the playlist.
Rather it should notice it's offline and act / display a message accordingly.
Side note, great work guys! I'm finding Koel extremely useful and lovely and would love to contribute if I can get up to speed.
@X-Ryl669 commented on GitHub (Feb 9, 2017):
There's already a ping feature in the PHP backend, so it might not be very hard to do.
Please correct me if I'm wrong, but I think we should capture plyr's error and then try to ping the server and upon this error (not plyr's error alone since it sometimes fails for whatever reasons), put a "Disconnected" message on screen. Also need an interval to check the server presence regularly.
@phanan commented on GitHub (Feb 10, 2017):
Or we can make use of
navigator.onLinepresented in green browsers. What to do after that is more important. Should we disable everything with an overlay, or somehow implement an offline queue for actions such as playlist-related, like/unlike etc.?@phanan commented on GitHub (Feb 10, 2017):
Now that I think about it, Koel can totally run offline, i.e. if you use it locally or from a machine in your LAN.
navigator.onLinewill fail in these cases I suppose. The documentation describes quite different behaviors per browser as well.@X-Ryl669 commented on GitHub (Feb 10, 2017):
BTW, even when
online, you could have reached the expiring time of the auth token and no other song fetching will work until you reconnect. Although can run offline, it's useless if you can't download songs, fetch artists and albums' info etc... None of those will fit in browser cache.So a real offline mode seems like a dream for now.
I deduce that a user message "Koel is orphan from its server, please help..." and stopping playing is the first action to do.
@phanan commented on GitHub (Dec 3, 2022):
This has landed (finally) in v6.5.2.