11

I've read different threads but never got to a clear conclusion, what are the differences, advantages and disadvantages of using user-scalable=no on case A or case B?

I'm going to do a responsive website, which case is better then?

CASE A:

<meta name="viewport" content="width=device-width, user-scalable=no">

CASE B:

<meta name="viewport" content="width=device-width">
Daniel Ramirez-Escudero
  • 3,425
  • 9
  • 40
  • 71
  • http://stackoverflow.com/questions/6397748/whats-the-point-of-meta-viewport-user-scalable-no-in-the-google-maps-api – CBroe Mar 12 '14 at 14:32

1 Answers1

19

You don't need to use user-scalable=no for responsive web design. You use it if you want your web app to feel more like a native app (in terms of zooming). You can control that users wont break your design if they zoom in. But technically, if you're doing responsive and your design breaks when zooming in, then you're not doing it right.

But, if you absolutely need to use it: "... however keep in mind that zooming is an important accessibility feature that is used by a lot of people. Turning it off should therefore only happen when really necessary, such as for certain types of games and applications." http://dev.opera.com/articles/view/an-introduction-to-meta-viewport-and-viewport/

AbeyMarquez
  • 545
  • 3
  • 12
  • 3
    **Be advised of some profits** of using `user-scalable=no` in responsive design - your "taps" (or clicks) will be handled faster on mobile http://stackoverflow.com/a/16910559/3810453 – Zanshin13 Mar 29 '17 at 12:29
  • Useful and definitely worth considering. – AbeyMarquez Mar 30 '17 at 19:06
  • 2
    “You can control that users wont break your design if they zoom in.” – You definitely got the Web wrong. It's not about you, it's about them. – Volker E. Jan 30 '18 at 07:24