要“用户可扩展=否”,或者不用于“用户可扩缩=否” [英] To "user-scalable=no" or not to "user-scalable=no"

查看:108
本文介绍了要“用户可扩展=否”,或者不用于“用户可扩缩=否”的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我读过不同的主题,但从来没有得出清楚的结论,对案例A或案例使用 user-scalable = no 有什么区别,优缺点B?



我打算做一个响应式网站,哪种情况更好?

 < meta name =viewportcontent =width = device-width,user-scalable = no> 

案例B:

 < meta name =viewportcontent =width = device-width> 


解决方案

您无需使用用户-scalable = no ,用于响应式网页设计。如果您希望您的网络应用更像本地应用(在缩放方面),则可以使用它。您可以控制用户放大时不会破坏您的设计。但从技术上讲,如果您在进行响应并且放大时设计会中断,那么您的做法就不对。


$ b但是,如果您绝对需要使用它:但是请记住,缩放是许多人使用的重要辅助功能,因此关闭时应该只在真正需要时才会发生,如某些类型的游戏和应用程序。
http://dev.opera.com/articles / view / an-introduction-to-meta-viewport-and-viewport /


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"> 

解决方案

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/

这篇关于要“用户可扩展=否”,或者不用于“用户可扩缩=否”的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆