Bug 5752 – Player Settings - Remote Controls - no way to set

Bug 5752 - Player Settings - Remote Controls - no way to set

Summary:

Player Settings - Remote Controls - no way to set

Status:	RESOLVED INVALID

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Web Interface
Version:	7.0
Platform:	PC Ubuntu Linux

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Squeezebox QA Team email alias

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-10-10 08:28 UTC by Mark Lanctot
Modified:	2007-10-10 11:18 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
No Save Settings button... (27.10 KB, image/png) 2007-10-10 08:31 UTC, Mark Lanctot	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Mark Lanctot 2007-10-10 08:28:11 UTC

The Player Settings - Remote Controls window in 7.0a1 has no "Save Settings" button so any changes are ignored.

This is on a screen set at 1024 X 768.

Comment 1 Mark Lanctot 2007-10-10 08:31:25 UTC

Created attachment 2245 [details]
No Save Settings button...

I should mention this is on SwiftWeasel 2.0.0.7 (Speed-optimized Firefox) on Ubuntu Linux 7.04 x86_64, although SqueezeCenter is running on Ubuntu Linux 7.04 32-bit.

SqueezeCenter Version: 7.0 - 13701 - Debian - EN - utf8
Server IP address: 192.168.1.8
Perl Version: 5.8.8 i486-linux-gnu-thread-multi
MySQL Version: 5.0.38-Ubuntu_0ubuntu1

This is the 10/10 nightly build.

Comment 2 KDF 2007-10-10 08:38:15 UTC

works for me, on the proper firefox.
What's the "Done" button for??  got custom strings?

Comment 3 Mark Lanctot 2007-10-10 08:45:53 UTC

Yes, it works for me on proper Firefox as well.

I'm not sure what the "Done" text is, no I don't have custom strings but the SwiftWeasel developer might have put some in.

What's odd is after loading the page in FF, the page in SwitftWeasel is now fixed, so it might have been some sort of caching going on?

OK to close then, sorry!