Bugzilla – Bug 5634
Use player cookie instead of url param
Last modified: 2011-11-06 23:22:56 UTC
I'm thinking it may save us a lot of effort spent on modifying the DOM on player change if we were to use the cookie at all times. This way, the chooser would simply set the current player and all links would operate on that player. The exception would be when the playerid param is used to do something specific to another player, such as the settings links in the classic skin. As part of bug 5621, we may need a dual cookie that keeps the last selected as well as the curently active player, as it may be possible that the last selected is not available in the currently connected players so we need to pick one that is. However, when the last selected does show up, the chooser can be updated. That, or we keep the last selected as the chosen player, and show something on the UI to indicate that the player is not found. the user can then select another player, wait for the connect (eg start softsqueeze) or find out why the player is not currently showing up.
Might be an issue with Pocket IE and other stripped down browsers?
disappointing, but then will those same browser work with Default skin now that it relies on extjs? perhaps its something we can do only with 'advanced' skins?
No, stripped down browsers which fail to load Default will be redirected to Classic. Did you mean to use cookie for Default only or globally in all skins?
Default, fishbone, probably Nokia770 skins. All heavily use JS and likely wouldn't work on stripped browsers anyway. It should make for a quicker player change. I thought one problem would be that you could no longer see the active player in the url, but the js use does that anyway.
I expect that we'll look at this post 7.0
Unassigned bugs cannot have a priority.