>>I had reached that as conclusion when trying out on tablet, resetting something and going back to desktop.
>>
>>A better place IMO for such settings would be one of the newer browser storages like IndexedDB (as WebSQL was killed and is only found on Google/Webview implementations and Gears is gone), even if the expected speedup from local caching sometimes is/was not as expected. A server side option would be to remember device/browser specific settings for each user.
>>
>>Benefit would be for the user to see same settings as last time set with that browser on that machine, which could evolve into different settings for different devices. Output switching from external to laptop screen would not be handled (unless using 1 browser for external, 1 different for internal screen usage) but would start to enable users to fit UT usage to each device in posession.
>>
>>If the above is unclear, don't hesitate to ask for specifics.
>
>Thanks for the feedback

You are welcome. The managment-speak of the above is that at least for me UT usage stays on 1 device only, even if I have 3 machines at my desk and for other/normal stuff am borderline addicted to my 2 Nexus tablets. Did try UT a few times on them (and on iPad mini and 10' tablet), but the fiddling to get agreeable settings was always blown away when switching devices. Hence I never look into UT unless at my working place. NOT ideal if you hope for quick checkins via any device currentky at hand ;-))