Bugzilla – Bug 5512
Player Settings page is not too users friendly.
Last modified: 2007-10-02 22:15:40 UTC
System Info: Gateway, P4, 1.97 GHz, 1.25 GB of RAM, XP SP2 ENU VERSION INFO SlimServer Version: 7.0a1 - 12905 - Windows XP - EN - cp1252 Perl Version: 5.8.8 MSWin32-x86-multi-thread MySQL Version: 5.0.22-community-nt Steps to Reproduce: 1. Start SlimServer and open the web interface. 2. Click the "Player Settings" button on the bottom right. 3. A bare bone IE window pops up. 4. Notice the bottom line is half cut off. It does not look like the bottom of the page. 5. Also, on this bare bone IE, if the user wants to change some settings of the browser, he/she cannot not do that. There is no menu bar or anything on it. The classic SLimServer web skin is easier to work with.
Created attachment 2141 [details] Player Setting page is a bare bone IE page.
Settings pages aren't implemented yet. This is not a bug, just a missing feature :-)
*** Bug 5513 has been marked as a duplicate of this bug. ***
*** Bug 5508 has been marked as a duplicate of this bug. ***
aside from a badly formatted PWD (which should be set to disappear on the new window) it looks much better if you call teh [% webroot %] path for settings pages. the hardcoded EN ones are a bit shocking as a placeholder :)
Kevin - I did hardcode EN as the Default's scripts loaded with pageheader etc. don't like the old JS (and vice-versa). But Classic would probably have been a nicer alternative :-). But I hope to start working on the settings pages very soon...
On Windows Vista (IE 7) the Save button is completely missing from view unless you happen to know to tab off of the last field - then it shows up, etc. Originally you have NO scroll bars so you cannot scroll down to it, etc. Don't want to start a new report on this since it appears that you already know that you have to work on it. THANKS!
Dan, could you have one of your people try reproducing this symptom from comment 7 on Vista? Thanks!
No need to verify anything: the settings pages haven't been implemented. Nothing to fix, we just have to implement it first. I'm going to to close settings related pages as INVALID as long as we haven't done them.