Preference Cookie?

[michelgo]

Nice solution.

But it is not ideal if we want to let the user stay on the desktop website after using the force=1 GET parameter. (Many users like to browse the desktop version of a website even if displayed on a mobile device.)

You may want to consider creating a "preference cookie" when that parameter is used.

In such a scenario, the desktop website can offer a link to the mobile version if our user wants to go back to that version.

[matthewrobertson]

+1 If you have a multipage application you need the force to persist across page loads. I might take a whirl at adding this.

[0xadri]

+1, saving the user choice in a cookie seems only logical.
HTML5 provides a local storage so this might be the easiest way to go.
See how this similar project did it https://github.com/chrismorata/Responsive-View-Full-Site/blob/master/js/rwd-display.js

[borismus]

I'm not maintaining this project now, but would accept a pull request.
Thanks!

On Tue, Jul 15, 2014 at 10:43 AM, Adrien be [email protected]
wrote:

+1, saving the user choice in a cookie seems only logical.
HTML5 provides a local storage so this might be the easiest way to go.
See how this similar project did it
https://github.com/chrismorata/Responsive-View-Full-Site/blob/master/js/rwd-display.js

—
Reply to this email directly or view it on GitHub
#8 (comment).

[0xadri]

Does anybody does? seems like almost nothing happened since April 2013... https://github.com/borismus/device.js/graphs/contributors

[joethuoo]

well i think if i don't want the user to have the option of switching to desktop version then i suppose device.js is proper.

[joethuoo]

hold on this library is awesome!!! :-)