Bug 8705 - Feature: Apply/Save width of "Now Playing" pane
: Feature: Apply/Save width of "Now Playing" pane
Status: RESOLVED DUPLICATE of bug 15995
Product: Logitech Media Server
Classification: Unclassified
Component: Web Interface
: 7.3.3
: All All
: P5 minor with 2 votes (vote)
: 7.5.1
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-11 11:33 UTC by Bruno Fernandes
Modified: 2010-04-12 14:11 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Fernandes 2008-07-11 11:33:15 UTC
I propose a feature to allow SAVING the current width (in pixels) of the Now Playing half of the web interface.  Once saved, the interface will be restored such that the Now Playing comes up at the saved size and the menu half as the remainder of the window browser window, regardless of its starting size.

Background:
Currently the default web interface starts up with the window divided in two. The left half for navigating menus and music and the right half for the Now Playing list.

When the web browser window is resized, the width of the Now Playing list is fixed at the pixel size it was started in - only the menu pane widens/contracts.

The width relationship between the two "halves" can be altered by dragging the dividing line between them to one or the other side but the size is lost/forgotten as soon as the window is closed.

My proposal would either save the information in a cookie for the browser or back to the server like the other prefs are saved.
Comment 1 Michael Herger 2008-07-13 04:56:32 UTC
I seem to never resize my browser window or I would have implemented this long ago. Thanks for the reminder.
Comment 2 Bruno Fernandes 2008-07-13 08:28:01 UTC
I don't resize my browser that much either.  But I do have to re-open a SC session every now and then, and that's when you see the issue because the relationship of the two SC halves always comes up 50/50.

Comment 3 Michael Herger 2008-07-24 03:57:56 UTC
I'm sorry, this has to wait a bit longer. I assume there will be more feedback on how this should be implemented as soon as 7.1 hits the masses.
Comment 4 Michael Herger 2008-08-28 14:18:26 UTC
*** Bug 9317 has been marked as a duplicate of this bug. ***
Comment 5 Michael Herger 2008-09-04 08:10:37 UTC
change 23036 - remember the playlist's width (storing it in a cookie). I hope we won't have to make this optional... Let's see what people think.
Comment 6 Bruno Fernandes 2008-09-07 20:24:40 UTC
So far the feature is working beautifully for me using either Safari 3.1 or Firefox 3.01

Thanks for adding this Michael.
Comment 7 Jim McAtee 2008-09-10 20:49:09 UTC
I love it.  Could this safely be merged into 7.2?
Comment 8 Bruno Fernandes 2008-12-05 07:49:31 UTC
Testing in Safari 3.2.1 (and prior versions)

The width saving feature is not persistent long-term and is lost every few days.

It works over multiple browser sessions (quit and restart browser) but every few days (don't have exact number yet) the setting is completely lost.
Comment 9 Bruno Fernandes 2008-12-05 07:52:38 UTC
Could it be the expiration date of the cookie used to store this property?

Let me know if I should open a different report or if using this original one is acceptable.
Comment 10 Michael Herger 2009-02-16 13:55:53 UTC
*** Bug 11103 has been marked as a duplicate of this bug. ***
Comment 11 Jim McAtee 2009-02-16 14:05:44 UTC
It's now broken in Firefox 3.0.6.
Comment 12 Jim McAtee 2009-02-16 14:14:37 UTC
I'm seeing the same thing in 7.3 trunk, so the version should be changed.
Comment 13 Michael Herger 2009-02-16 23:17:47 UTC
change 25036 - need to define stateId, or the panel's state won't be saved.
Comment 14 Michael Herger 2009-02-16 23:20:46 UTC
Note to myself: better read changelogs when updating ExtJS:

- Ext.Component (Doc Updates)
State management now ignores auto generated ids.
Comment 15 James Richardson 2009-06-17 09:35:21 UTC
This bug has been fixed in the 7.3.3 release version of SqueezeCenter!

If you haven't already. please download the new version from http://www.logitechsqueezebox.com/support/download-squeezecenter.html 

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Comment 16 Bruno Fernandes 2009-07-20 14:00:49 UTC
This is still broken in SC 7.3.3 final (27044).

Testing with Safari version 4.0 final release in Mac OS 10.5.7

The pane width is saved but only lasts an indeterminate amount of time.  Unfortunately I don't know exactly how long. It will work through quitting the browser and restarting the computer. It will even work for a few days.  But then, poof, the division is back in the middle.

For additional reference, I have the address of SC on the lan mapped to "sb" in my hosts file, so that in the browser URL, I can reach SC simply with "http://sb:9000"
Comment 17 Michael Herger 2009-07-29 05:22:32 UTC
This is working fine for me.

> The pane width is saved but only lasts an indeterminate amount of time. 

Maybe it's Safari crashing which causes loss of cookies or something? Can you reproduce this on another browser?

QA - can you reproduce this?
Comment 18 Bruno Fernandes 2009-07-29 07:51:05 UTC
It's definitely not Safari crashing, as with the release version, I have yet to see a crash in the past month.

I'll begin side-by-side testing with Firefox 3.x, but it might very well be this problem is specific to Safari 4.x - it may even have something to do with its Top Sites sites display (which will refresh the page contents even without you navigating specifically to that page/site).  I keep my SC address permanently as one of the thumbnails on the Top Sites page. 

However it might not be 4.x specific at all since I did find back with version 3.2.1 that the feature only lasted a few days.

When does the Cookie expire?
Comment 19 Ross Levine 2009-10-07 14:50:40 UTC
Is this still an option with 7.4?
Comment 20 Jim McAtee 2009-10-07 14:54:19 UTC
(In reply to comment #19)
> Is this still an option with 7.4?

Still works for me in 7.4 using Firefox.  I don't think it was ever an 'option', if you mean a user setting.

I do see that it frequently gets lost, though.  Not always, but frequently.
Comment 21 Bruno Fernandes 2009-10-07 14:54:56 UTC
This is not an "option" insofar as there's no setting to control it in SS's preferences.  It's a feature that is supposed to work automatically and all the time in every browser that supports cookies.

The feature is still working in 7.4 and I'm in the process of verifying whether or not the width setting is forgotten after a period of time as I mentioned earlier.
Comment 22 Ross Levine 2009-10-08 11:18:48 UTC
Ahh thanks guys I see it now, it just doesn't work in IE. Works for me with firefox, but I only waited a few minutes. Thanks Bruno for verifying.
Comment 23 James Richardson 2009-10-30 08:52:28 UTC
Bruno: How does this look to you, can we close this bug now or are you still investigating it?
Comment 24 Bruno Fernandes 2009-10-30 09:34:44 UTC
For the life of me I can't recall with 100% certainty if 7.4 still had the issue, but so far the width has remained as set with 7.4.1.

Let me monitor it until the end of next week and then  update the status on it.  With Safari I keep SS as one of my tiles in Top SItes, so it's easy to see when the width ratio has changed, even if I'm not opening the SS page manually at the moment.
Comment 25 James Richardson 2009-10-30 10:06:14 UTC
Marking as fix then, if you still have issues update and reopen the bug.

thanks for looking into this.
Comment 26 Bruno Fernandes 2009-10-30 10:59:47 UTC
Well, it didn't take that long. :)  Problem reproduced with 7.4.1 running on Windows and browsing with Safari 4.0.3 in Mac OS.

The width setting is lost in a regular, but still what appears like a random basis.  The width way fine as I started playing a number of tracks.  I kept SB open in a tab and all was well since I last updated the bug earlier today.  I closed that tab and opened a new tab maybe 30 minutes later.  Width pref was now at default (50/50).
Comment 27 Jim McAtee 2009-10-30 11:44:28 UTC
P5/minor/Future = WONTFIX.
Comment 28 Michael Herger 2010-04-12 03:43:11 UTC
bug 15995 actually is a bug of this one. But fwiw: that's fixed now. The code was indeed defaulting to 7 days expiry.

*** This bug has been marked as a duplicate of bug 15995 ***
Comment 29 Bruno Fernandes 2010-04-12 14:11:46 UTC
I'm glad to hear it's fixed, even if it's been well over a year since I suggested what the problem was (cookie expiration date).

I'll test it when I can get my hands on the relevant release.