发表新帖
发表新帖

What's the point of 'meta viewport user-scalable=no' in the Google Maps API

后端 未结
关注
4 946
陌清茗
陌清茗 2020-12-04 08:13

I\'m using the Google Maps JavaScript API V3 and the official examples always have you include this meta tag:
相关标签:
4条回答
  • 傲寒
    2020-12-04 08:49

    You should not use the viewport meta tag at all if your design is not responsive. Misusing this tag may lead to broken layouts. You may read this article for documentation about why you should'n use this tag unless you know what you're doing. http://blog.javierusobiaga.com/stop-using-the-viewport-tag-until-you-know-ho

    "user-scalable=no" also helps to prevent the zoom-in effect on iOS input boxes.

    0 讨论(0)
  • 一整个雨季
    2020-12-04 08:52

    On many devices (such as the iPhone), it prevents the user from using the browser's zoom. If you have a map and the browser does the zooming, then the user will see a big ol' pixelated image with huge pixelated labels. The idea is that the user should use the zooming provided by Google Maps. Not sure about any interaction with your plugin, but that's what it's there for.

    More recently, as @ehfeng notes in his answer, Chrome for Android (and perhaps others) have taken advantage of the fact that there's no native browser zooming on pages with a viewport tag set like that. This allows them to get rid of the dreaded 300ms delay on touch events that the browser takes to wait and see if your single touch will end up being a double touch. (Think "single click" and "double click".) However, when this question was originally asked (in 2011), this wasn't true in any mobile browser. It's just added awesomeness that fortuitously arose more recently.

    0 讨论(0)
  • 谎友^
    2020-12-04 09:02

    Disabling user-scalable (namely, the ability to double tap to zoom) allows the browser to reduce the click delay. In touch-enable browsers, when the user expects the double tap to zoom, the browser generally waits 300ms before firing the click event, waiting to see if the user will double tap. Disabling user-scalable allows for the Chrome browser to fire the click event immediately, allowing for a better user experience.

    From Google IO 2013 session https://www.youtube.com/watch?feature=player_embedded&v=DujfpXOKUp8#t=1435s

    Update: its not true anymore, <meta name="viewport" content="width=device-width"> is enough to remove 300ms delay

    0 讨论(0)
  • 名媛妹妹
    2020-12-04 09:10

    From the v3 documentation (Developer's Guide > Concepts > Developing for Mobile Devices):

    Android and iOS devices respect the following <meta> tag:

    <meta name="viewport" content="initial-scale=1.0, user-scalable=no" />

    This setting specifies that the map should be displayed full-screen and should not be resizable by the user. Note that the iPhone's Safari browser requires this <meta> tag be included within the page's <head> element.

    0 讨论(0)
 看不清?
提交回复
热议问题