This isn't likely to come up often, since generally different installations won't be on the same HTML5 origin, but it can make things really annoying to test and develop.
localsettings is inherently keyed only by origin (scheme, hostname, port), so an http://hostname/cadence-production/ and http://hostname/cadence-development/ client will share the same localstorage object. That gets iffy even before we get into the problem of changes in the configuration scheme, because it also messes with syncing on different servers (which only goes by username).
Suggested course of action: Include installation path in localstorage object name (but fall back to global name to avoid losing everybody's settings again).
This isn't likely to come up often, since generally different installations won't be on the same HTML5 origin, but it can make things really annoying to test and develop.
localsettings
is inherently keyed only by origin (scheme, hostname, port), so an http://hostname/cadence-production/ and http://hostname/cadence-development/ client will share the same localstorage object. That gets iffy even before we get into the problem of changes in the configuration scheme, because it also messes with syncing on different servers (which only goes by username).Suggested course of action: Include installation path in localstorage object name (but fall back to global name to avoid losing everybody's settings again).