Bugzilla – Bug 12173
Player selected in Settings becomes target in browse window
Last modified: 2010-04-07 00:31:23 UTC
With multiple players connected to a server, sometimes when you attempt to play or add tracks on one, they'll end up being sent to another player. I'm fairly certain that this is being caused by an interaction with the Settings page. When it's open, the current player in Settings will often end up being the target of commands in the browse pane. I can't reproduce it 100% of the time, but I have reproduced it on the two browsers that I've tried so far: Firefox 3.0.10 and Google Chrome 1.0.154.65 on Windows XP Pro SP3. Sometimes all it takes is opening the Settings page, changing the player in the Player tab, then going back and attempting to play something on the original player.
Michael: what logs should be enabled?
This is a client side (browser) issue. Nothing to log.
Punting skin related issues as the web UI should see another overhaul post 7.4.
Heh... here it is. Let's track this down for 7.6.
== Auto-comment from SVN commit #30456 to the slim repo by mherger == == https://svn.slimdevices.com/slim?view=revision&revision=30456 == Fixed Bug: 12173 Description: Player selected in Settings becomes target for browser actions. Consistently distinguish between the "player" variable (used in the player control web UI) and the "playerid" variable (used in settings). Only fall back to using player if no playerid is defined.
== Auto-comment from SVN commit #30485 to the slim repo by mherger == == https://svn.slimdevices.com/slim?view=revision&revision=30485 == Bug: 12173 Description: Player selected in Settings becomes target in browse window. Backport change 30456 from 7.6/trunk