Bugzilla – Bug 3707
Pane refresh errors don't recover
Last modified: 2008-12-15 13:07:34 UTC
I've listed this as trivial, which it is. I've no idea if the solution is trivial, or even possible. On my desktop PC I usually keep a Firefox browser tab open to my SlimServer. When I go back to the tab after a long period of inactivity (several hours with no music playing on the selected player) I often see that one or both of the right-hand 'status' and 'playlist' panes are displaying a Firefox timeout error page. Refreshing within either pane or else refreshing the entire page will clear this up, but it's an inconvenience. If I'm thinking clearly, the problem is that the loaded pages within these two panes refresh themselves. When the page is unable to be loaded for whatever reason then that chain is broken and the panes keep the error message displayed until the user refreshes them manually. The browse pane is never affected because it doesn't refresh itself, so even if the server is completely unavailable it doesn't cause an error there. Could the javascript for the refreshes of the two right-hand frames be moved to the browse frame or even to the frameset pages?
not as trivial as it may seem. the refresh timing is dependant on the current song time, and is updated on each refresh. without some sort of refresh on the page that contains the javascript, we'd lose the updates that set the refresh near teh track boundary. Ajax mitigates this somewhat, in that it can avoid the blank page, but some aspects of the ajax update are still lost when the connection is gone for a length of time, whether by server stoppage or client going into standby
I've seen this as well. I'll assign it to Dan for now to muse upon.
this should now be fixed in 6.5.1, at least for Default, Fishbone, and Nokia770. All of these use ajax for handling the refresh. Default has the most minimal case that delays page refresh until there is a valid response from the server on a small 'ping' page load. Works in 6.5.0 for Firefox, bug IE required a later fix. See bug 4192
This bug appears to have been fixed in the latest release! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look. Make sure to include the version number of the software you are seeing the error with.