474

I've tried all three of these to no avail:

<meta name=”viewport” content=”width=device-width; initial-scale=1.0; maximum-scale=1.0; user-scalable=0;” />

<meta name=”viewport” content=”width=device-width; initial-scale=1.0; maximum-scale=1.0; user-scalable=false;” />

<meta name=”viewport” content=”width=device-width; initial-scale=1.0; maximum-scale=1.0; user-scalable=no;” />

each are different values I found recommended by google searching or SO searching, but none of the 'user-scalable=X' values seem to be working

I also tried comma delimiting the values instead of semicolon, no luck. Then I tried ONLY having the user-scalable value present, still no luck.


UPDATE

Got this from Apple's site and it works:

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

it turns out that the problem was the non-standard quotes because I had copied the meta tag from a website that was using them, whoops

Tomerikoo
  • 18,379
  • 16
  • 47
  • 61
MetaGuru
  • 42,847
  • 67
  • 188
  • 294
  • 10
    If you're making a game, then possibly controlling zooming is valid. However in nearly all other cases it should be strongly discouraged. Unfortunately it has become standard practice for a lot of mobile developers. If a user wants to zoom in to be able to read text more easily etc. preventing them from doing so isn't very nice. – user2268788 Jan 23 '15 at 01:40
  • 110
    We are disabling zoom on a mobile web based application. You can't zoom in Native iOS apps and it's not required in our web application. If your site or app is mobile optimised then your users won't need to zoom. There are always use cases for disabling zoom. It doesn't have to always be one way or the other. – Bradley Flood Feb 04 '15 at 23:58
  • 2
    Pinch to zoom was made popular (not invented) in 2007 when the iPhone was unveiled to solve the problem when mobile websites only offered user-agent adaptive versions of their site or javascript event listener tricks instead of the responsive design versions we take for granted today thanks to CSS3 in 2008. Prior to our mobile HTML 5 rich websites, the internet on a mobile device was considered "the baby web" & everything was tiny to read. Now, when there's an that requires to zoom ANY content or app, they should use the native device zoom here: https://support.apple.com/en-us/HT203332 – Evan Oct 23 '15 at 20:39
  • 19
    Yea I'm not following the line of logic that disabling zoom on a mobile optimised site is a *bad thing*. What's far worse is having the viewport accidentally pan around because the screen is picking up accidental pan and zoom input on a site that doesn't require you to zoom anyway. Realistically if your users are needing to zoom into content on your mobile optimised site then the problem is the design, not the lack of zoom. – Nathan Hornby Jan 28 '16 at 14:45
  • try shrink-to-fit=no in viewport meta tag – ursuleacv Apr 18 '16 at 19:47
  • 7
    @NathanHornby: The problem of disabling zoom is a lack of respect of user's preferences. Different users prefers different text sizes, younger audience with good eyesight might prefer to see more content, while audience with poor eyesight can't use anything that doesn't have giant text. Other people have Parkinsons but still have good eyesight, so they prefer extra large buttons but don't benefit from large text in general. – Lie Ryan Oct 10 '16 at 12:34
  • 3
    @Lie Ryan These are very good use-cases, however I feel that they're still mostly accounted for in good design. Global accessibility attributes like text size and *screen* zoom I definitely see as user preference - but the ability to pan/zoom on a webpage isn't an accessibility feature, it's an interface feature. Also keep in mind that the Safari zoom has an upper-limit, and it's not that high - so it doesn't work very well as a 'magnifying glass' for users with sight issues anyway. Accidental pan/zoom is an issue *all* users face, including those with greater accessibility needs. – Nathan Hornby Oct 11 '16 at 13:26
  • @LieRyan mobile first, and accessibility practices. – Mark Carpenter Jr May 22 '17 at 15:53
  • 3
    @NathanHornby: If your design was so perfect that it suited all users all the time, people wouldn't try to zoom in. If they're trying to zoom in, then they obviously have some reason to do so. Unless you have some specific technical reason to *need to* block pinch zoom, DO NOT BLOCK BLOCK PINCH ZOOM! – user1751825 Jul 18 '17 at 08:22
  • 2
    @user1751825 you seem to have missed me using the word 'accidentally'. If your website is designed correctly and mobile optimised, then pinch-zooms are almost definitely *accidental*. By blocking the ability you are preventing user error. If your users need to pinch-zoom on your mobile optimised website then you have done something wrong. This subject is a dead horse. – Nathan Hornby Jul 19 '17 at 12:50
  • 6
    @NathanHornby It doesn't mean the designer has done something wrong necessarily. It simply means the user, for whatever reason, wants to zoom in. Pinch-zoom is a standard feature of all touch-screen phones. Any user who owns such a phone, knows how to use it. I know it's an old question, but I still am constantly frustrated by know-all developers who insist on breaking the functionality of my phone because they think it makes their designs look better. – user1751825 Jul 20 '17 at 04:02
  • 2
    @user1751825 **It has nothing to do with making anything look better**, as covered it's preventing *undesired behaviour*. I will repeat, a *correctly designed* mobile optimised website has no requirement to be pinch and zoomed. If the issue is a11y then pinch and zoom is a poor solution, it's not how users with sight issues use mobile phones. Literally the only purpose of pinch and zoom in the browser is to enable a user to navigate media and pages that have NOT been optimised for mobile. Turning off features for a purpose not required to avoid unintended behaviour is good design. – Nathan Hornby Aug 24 '17 at 10:00
  • 1
    IMO this is an Apple driven propaganda masquerading as an accessibility principle via WCAG. Pinch to zoom is hack to circumvent poor design choices at initial render to begin with. https://stackoverflow.com/questions/49589861/is-there-a-non-hacky-way-to-prevent-pinch-zoom-on-ios-11-3-safari – Marvin Danig Apr 02 '18 at 16:53
  • 1
    Wow I havent seen this on SO yet - a question based on a typo which should be closed, can have almost 300 upvotes. Because of a typo, lol! – Daniel W. Jun 06 '18 at 16:16
  • 1
    Browsers are used for more than just regular web pages ie WEB APPS. What about fullscreen drawing-on-a-canvas experiences, with fixed navigation elements? The user expects to have full gesture controls only within the canvas working area. However pinching a fixed header, they do not expect for the entire page container to go flying off in different directions. – Kalnode Jun 25 '20 at 12:47
  • 2
    Locking out zoom for users of web pages demonstrates a flagrant disregard for accessibility, regardless of if the content is "mobile optimized." It is impossible to "optimize" any content for all persons, and this is most especially true of those with vision issues. A site (or app for that matter) is not optimized if it does not allow the user to increase the minimum font size (at a minimum). The claim that "accidental panning" is worse is unsupported. There is no "one size fits all" in accessibility, and disabling zoom is a automatic failure. – Myndex Dec 23 '20 at 12:06

20 Answers20

813

Edit: may not work after iOS 10, please see touch-action based solution below.

Your code is displaying attribute double quotes as fancy double quotes. If the fancy quotes are present in your actual source code I would guess that is the problem.

This works for me on Mobile Safari in iOS 4.2.

<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no" />
DarkKnight
  • 5,651
  • 2
  • 24
  • 36
BoltClock
  • 700,868
  • 160
  • 1,392
  • 1,356
  • 13
    it was the fancy quotes, I had copied the tag from a website without noticing, thanks for pointing that out! – MetaGuru Dec 08 '10 at 16:49
  • This was great help. I was using "minimum-scale=1.0, maximum-scale=1.0" until I realized iOS 6 Safari was allowing pinch zoom on input fields but not on non-input pages. Adding "user-scalable=no" fixed it. – Adam Nov 01 '12 at 18:07
  • 5
    Perhaps this is at the long tail here but it might be worth pointing out that this needs to be applied at the "top level" page. If you have this meta tag applied to an iframe, it won't work unless the meta tag is also applied to the top-most page. – founddrama Feb 11 '13 at 14:43
  • Thanks for this. Lots of misinformation out there about this one. Your example works perfectly. – jamesnotjim Mar 11 '13 at 20:36
  • 4
    Why anyone would ever create a piece of software that creates fancy quotes is beyond me. – ASA Jun 23 '15 at 15:23
  • 6
    @Traubenfuchs: Typography. – BoltClock Jun 23 '15 at 15:24
  • do you also need to use ? – SuperUberDuper Aug 13 '15 at 10:34
  • 4
    This is a rather old answer and coming to the problem I had read that if you set user-scalable to no this would cause accessibility problems. As of iOS 10 it works fine, allowing the user to zoom if he wishes, but but not zooming the input box otherwise. No need to set large font sizes either. – David Jul 25 '17 at 22:19
  • 1
    @David: If it allows the user to zoom if he wishes, then it doesn't work anymore, does it? After all, the point of user-scalable=no is that it's supposed to *prevent* the user from manually scaling the viewport at all. – BoltClock Jul 26 '17 at 03:46
  • @BoltClock — It doesn't work the way it's intended to, but from my point of view it does exactly what I want. It prevents the automatic zoom when the user clicks in the input, but allows him to zoom himself (and repeatedly). I must admit I was surprised at the result when I added the three scale arguments to the content attribute in the meta tag. I've double-checked it on an iPhone 5 and 6, both running iOS 10.3.3. The pages in question uses an input of type=number, which is not part of a form, for example http://motif.gla.ac.uk/FTB-R/sigfigs.html . I haven't checked an input of type=text yet. – David Jul 26 '17 at 07:49
  • @BoltClock — I've just seen all the other comments/posts about Apple disabling user-scalable=no, so my initial comment, though meant to be helpful, was old news. Sorry. Clearly if you are in a different situation and have a good reason to want to suppress user pinch-zoom this is a bummer. For me the ability to prevent automatic zoom was all I cared about and is a major HCI improvement. – David Jul 26 '17 at 07:57
  • @David: Ah, I'm in agreement on that. – BoltClock Jul 26 '17 at 08:37
  • This answer doesn't work on newer iOS versions, as many have noted here in the comments. However, it *is* possible to get this working on newer iOS versions using the `touch-action` CSS property. See my answer: https://stackoverflow.com/a/62165035 – Feross Jun 03 '20 at 04:09
194

For the people looking for an iOS 10 solution, user-scaleable=no is disabled in Safari for iOS 10. The reason is that Apple is trying to improve accessibility by allowing people to zoom on web pages.

From release notes:

To improve accessibility on websites in Safari, users can now pinch-to-zoom even when a website sets user-scalable=no in the viewport.

So as far as I understand, we are sh** out of luck.

Mattis
  • 5,026
  • 3
  • 34
  • 51
  • 16
    What a terrible decision by Apple. Using a spinner with "-" and "+" buttons to decrement/increment a number now repeatedly zooms the page in and out on iOS Safari. The presses are being interpreted as double-tap to zoom, with no way to disable that. iOS Chrome working perfectly. Frustrating. – Paul Oct 23 '16 at 04:59
  • 5
    Although I'm screwed of that decision but I'm really happy from apple as a user as I wanted to force this feature in a lot of websites that were using small elements inside. – Bishoy Hanna Nov 08 '16 at 05:57
  • 21
    the world is going to hell – little tiny man Mar 28 '17 at 05:53
  • 5
    Oh jeez, who would've guessed? Another ridiculous choice made by Apple – Emil Rosenius Dec 11 '17 at 09:14
  • 8
    Leave it to Apple to force an accessibility "feature" on everyone instead of just adding an option for it in the **Accessibility** settings... – Lennholm Feb 19 '18 at 17:05
  • https://stackoverflow.com/questions/49589861/is-there-a-non-hacky-way-to-prevent-pinch-zoom-on-ios-11-3-safari – Marvin Danig Apr 02 '18 at 17:03
  • 2
    It is possible to get this working on newer iOS versions using the `touch-action` CSS property. See my answer: https://stackoverflow.com/a/62165035 – Feross Jun 03 '20 at 04:09
  • 3
    Apple hates web apps; they want us all to make native apps for iOS. That's why they keep Safari on the edge of obsolescence but still force everyone to use it. Native apps have no issue here; if you want an element to respond to pinch gestures, you allow them; otherwise you don't. Where's the "accessibility" concern there? It's all baloney. – Emperor Eto Jul 03 '21 at 20:11
  • Apple is trying to control the websites to increase the App Store profits with new Apps XD – Extrange planet May 29 '23 at 02:43
112

@mattis is correct that iOS 10 Safari won't allow you to disable pinch to zoom with the user-scalable attribute. However, I got it to disable using preventDefault on the 'gesturestart' event. I've only verified this on Safari in iOS 10.0.2.

document.addEventListener('gesturestart', function (e) {
    e.preventDefault();
});
David Zorychta
  • 13,039
  • 6
  • 45
  • 81
jeremypress
  • 1,186
  • 1
  • 7
  • 5
  • Nice one, hopefully it's a stable solution. – Mattis Oct 01 '16 at 21:31
  • This didn't work for me on iOS10, could you provide a running example? – Patrick Winkelmayer Oct 07 '16 at 11:01
  • 10
    On iOS 10, I found that this worked, but if you scroll the page and then pinch-zoom while still scrolling, it allows the zoom. Then you find yourself stuck at the new zoom level until you scroll again. So this doesn't look like a good solution unless your page body is not scrollable. :( – Rand Scullard Oct 07 '16 at 14:51
  • @RandScullard good catch, not sure how often that happens but it definitely does break this method. I would really only suggest overriding the default if you are providing your own way of zooming the page. – jeremypress Oct 10 '16 at 18:18
  • 1
    One caveat: the user can still double tap the screen which will/can zoom and is not caught by this. – Stephen Oct 22 '16 at 00:42
  • 1
    Still sometimes allows zooming by double-tapping the screen. :( – Jarzka Nov 24 '16 at 11:01
  • 4
    What is the "double tap" equivalent to `gesturestart`? [dblclick](https://developer.mozilla.org/en/docs/Web/Events/dblclick)? – lowtechsun Jan 19 '17 at 18:32
  • It's worth noting Arthur's answer http://stackoverflow.com/a/42780478/1283556 addresses the scroll problem, because it allows you to zoom out without having to be scrolling again – Craig Mar 27 '17 at 15:08
  • 3
    Another note, if you want to disable the double tap aspect of zooming. Mobile Safari also supports 'touch-action: manipulation' (falls under 'basic support', which disables double tap events. Documentation here: https://developer.mozilla.org/en-US/docs/Web/CSS/touch-action – jeremypress Jul 30 '17 at 18:27
  • I don't know guys but this sounds like a bad idea. I think apple's decision to not disable zoom was for a good reason. It's the same as `outline: none` Some users will suffer. – Arnaldo Capo Sep 25 '17 at 09:45
  • Works with iOS version 11 as well – CandleCoder Oct 12 '17 at 07:09
  • This worked for me solving a problem with a pinch zoom image in a website....Thank You – Gabbr Issimo Feb 08 '19 at 15:04
  • 1
    Works on iOS 15 – Murhaf Sousli Oct 10 '21 at 20:46
86

Using the CSS touch-action property is the most elegant solution. Tested on iOS 13.5 and iOS 14.

To disable pinch zoom gestures and and double-tap to zoom:

body {
  touch-action: pan-x pan-y;
}

If your app also has no need for panning, i.e. scrolling, use this:

body {
  touch-action: none;
}
Feross
  • 1,541
  • 14
  • 17
17

for iphones safari up to iOS 10 "viewport" is not a solution, i don't like this way, but i have used this javascript code and it helped me

 document.addEventListener('touchmove', function(event) {
    event = event.originalEvent || event;
    if(event.scale > 1) {
      event.preventDefault();
    }
  }, false);
Arthur Tsidkilov
  • 5,401
  • 2
  • 21
  • 18
17

I got it working in iOS 12 with the following code:

if (/iPad|iPhone|iPod/.test(navigator.userAgent)) {
  window.document.addEventListener('touchmove', e => {
    if(e.scale !== 1) {
      e.preventDefault();
    }
  }, {passive: false});
}

With the first if statement I ensure it will only execute in iOS environments (if it executes in Android the scroll behivour will get broken). Also, note the passive option set to false.

José Antonio Postigo
  • 2,674
  • 24
  • 17
10

I managed to stop this behavior by adding the following to the HTML header. This works on mobile devices, as desktop browsers support zooming when using the mouse wheel. It's not a big deal on desktop browsers but it's important to take this into account.

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

and the following rule to the CSS stylesheet

html {
 -webkit-text-size-adjust: none;
 touch-action: manipulation;
}
imelgrat
  • 2,407
  • 1
  • 12
  • 17
10

Actually Apple disabled user-scalable=no on latest iOS versions. I tried as guideline and this way can work:

body {
  touch-action: pan-x pan-y;
}
Pham Duc Toan
  • 149
  • 1
  • 3
9
user-scalable=0

This no longer works on iOS 10. Apple removed the feature.

There is no way yo can disable zoom website on iOS now, unless you make gross platform app.

angry kiwi
  • 10,730
  • 26
  • 115
  • 161
  • Such a bummer... Any idea why they removed this? – Stephen Tetreault Feb 05 '17 at 21:19
  • 8
    @smt they don't want web experience to compete with app experience on the app store. – Marvin Danig Apr 05 '18 at 23:51
  • 4
    @marvindanig yes... since they take 99$ fee to produce an app that could else easily be made an more accessible web page application for all platform. Also of Apple cannot like a "web experience", if it means users + devs can avoid the walled garden. Its all about power and money of Apple :( – humanityANDpeace Sep 13 '18 at 10:54
  • 1
    It is actually possible to get this working on newer iOS versions. See my answer: https://stackoverflow.com/a/62165035 – Feross Jun 03 '20 at 04:08
8

Try adding the following to your head-tag:

<meta name="viewport" content="width=device-width, initial-scale=1.0, 
minimum-scale=1.0, maximum-scale=1.0, user-scalable=no">

additionally

<meta name="HandheldFriendly" content="true">

Finally, either as a style-attribute or in your css file, add the following text for webkit-based Browsers:

html {
    -webkit-text-size-adjust: none
}
Lorenz Lo Sauer
  • 23,698
  • 16
  • 85
  • 87
5

This works fine in IOS 10.3.2

    document.addEventListener('touchmove', function(event) {
        event = event.originalEvent || event;
        if (event.scale !== 1) {
           event.preventDefault();
        }
    }, false);

thank you @arthur and @aleclarson

Nikhil Gowda
  • 417
  • 5
  • 16
3

sometimes those other directives in the content tag can mess up Apple's best guess/heuristic at how to layout your page, all you need to disable pinch zoom is.

<meta name="viewport" content="user-scalable=no" />
Alex Borsody
  • 1,908
  • 9
  • 40
  • 74
3

In Safari 9.0 and up you can use shrink-to-fit in viewport meta tag as shown below

<meta name="viewport" content="width=device-width, initial-scale=1.0, shrink-to-fit=no">
ursuleacv
  • 1,119
  • 14
  • 16
3

As mentioned this solution basically works as of late 2020:

document.addEventListener(
    'gesturestart', (e) => e.preventDefault()
);

But the downside is that while you are scrolling you'd still be able to pinch and then it gets stuck. The solution is to disable scrolling.

body {
    overflow: hidden;
}

But, what if you still wanted the page to be scrolled? You can still do it with another <div> set as overflow:auto:

<body>
    <div id='app'></div>
</div>

and then

body {
    overflow: hidden;
}

 #app {
     -webkit-overflow-scrolling: touch;
      height: 100vh;
      height: -webkit-fill-available;
      overflow: auto;
 }
amin
  • 3,672
  • 5
  • 33
  • 61
1

I tried all above things but this worked for me on IOS devices:

<meta name="viewport" content="width=device-width, initial-scale=1.0, height=device-height, minimum-scale=1.0, user-scalable=0">
0

As of today (Oct. 2022) with iOS 14.8, the ONLY way I could completely prevent the double tap zoom was this:

document.addEventListener("click", (e) =>
        {
            e.preventDefault();
        })

Even this:

* {
    touch-action: none !important;
}

(which is obviously not realistic, but just for demonstration purposes) wasn't enough in every case. It turned out that any for element on which I had handled click, double tapping on it would cause a nearly irreversible zoom-in, completely ignoring the touch-action setting. But if I called preventDefault() in the click handler, it would not zoom. So, doing this at the document level so far seems to be enough, so that I don't have to do it every time I handle click.

I have no idea what side effects this might have, but I'm sure folks will chime in if they think of any.

Emperor Eto
  • 2,456
  • 2
  • 18
  • 32
  • Doesn't this disable clicking any links? – Hashim Aziz Apr 13 '23 at 18:26
  • @HashimAziz I believe that's right yes. This is really only appropriate for SPAs with totally custom controls. But of course that's probably the only scenario where it's appropriate to disable iOS's zoom. Anyway, I do not deny this is by no means ideal and if anyone knows a better way to do this and have it work on newer iOS I'd be happy to use it! – Emperor Eto Apr 13 '23 at 19:18
0

2023 Update: on accessibility and the current state of Safari IOS

We had an auto-zoom issue with an input focus in a form, in Safari iOS. Solving the issue turned out to be more complex that we expected.

Quoting @haltersweb below:

"In order to comply with WAI WCAG 2.0 AA accessibility requirements you must never disable pinch zoom. (WCAG 2.0: SC 1.4.4 Resize text Level AA"

If the accessibility requirements don't sway you, the 9 point penalty incurred in Google Lighthouse for accessibility requirements violations — with the corresponding SEO downgrade – will give you some pause. Yes, Chrome Mobile is affected. Do not disable pinch zoom.

There are a couple of ways to deal with this issue that we tested and work (kudos to Rick Strahl for his research and blogpost):

  • Make sure that your input fields have font-size: 16px or greater.
  • Use maximum-scale=1 in the viewport meta tag selectively for iOS Safari.

Although the second solution sounds promising and we didn't want to deal with changing the design of the inputs, getting the font-size to 16px is the appropriate way to deal with this. It is always better to abstain from introducing hacks that in the end, you'll have to maintain for many years, and that will come with unintended consequences.

ganar
  • 627
  • 8
  • 17
-1

I foolishly had a wrapper div which had a width measured in pixels. The other browsers seemed to be intelligent enough to deal with this. Once I had converted the width to a percentage value, it worked fine on Safari mobile as well. Very annoying.

.page{width: 960px;}

to

.page{width:93.75%}

<div id="divPage" class="page">
</div>
Welshboy
  • 318
  • 4
  • 10
-2

In order to comply with WAI WCAG 2.0 AA accessibility requirements you must never disable pinch zoom. (WCAG 2.0: SC 1.4.4 Resize text Level AA). You can read more about it here: Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile, 2.2 Zoom/Magnification

haltersweb
  • 3,001
  • 2
  • 13
  • 14
  • 13
    This is not an answer.. and many clients yet ask to block zoom.. so I can't take this as a general rule –  Jun 16 '15 at 17:47
  • 10
    Accessibility zoom is not the page's (neither any app for that matter) responsibility. It is the operating system's responsibility to provide an accessible zooming tool. Every OS nowadays provides such feature, which applies as a *screen zoom*, and it should not interfere with the page's zooming itself, because this is not intended for accessibility. – Bruno Finger Jun 19 '15 at 18:02
  • 1
    I disagree with the comments above. I think disabling pinch-zoom in iOS and Android is a clear fail criterion for 1.4.4 for WCAG Level AA. But like a lot of things with WCAG, it is debatable. – Lachlan McDonald Aug 24 '15 at 01:23
  • 4
    There are always valid use cases for stuff like this. For some reason, pretty much all web literature seems to assume that the web is only for making blogs. Just as there are valid use cases for JavaScript's `eval()`, so are there for disabling zooming. I am using it for a web-app that is used in combination with a Bluetooth scanner, to prevent the page zooming when a barcode is scanned. – user5670895 Sep 30 '15 at 19:09
  • 3
    I completely agree with the aims of the accessibility recommendations, but there's no question that there are times when zoom is not desired or needed, or may even break the user experience. Plus, you know, clients. – Chuck Le Butt Oct 12 '15 at 17:37
  • 4
    I'd say that in a html/javascript app, those guidelines do not apply. After all, would a native app let you zoom in and out? – Jörgen Sigvardsson Dec 30 '15 at 11:19
  • You raise an interesting point Jorgen. It all depends on whether or not the HTML site in question is required to follow the W3C's WCAG 2.0 AA rating. Here is an interesting read by the W3C: https://www.w3.org/TR/mobile-accessibility-mapping/#zoom-magnification. It raises a distinction between OS-level features and browser-level features. It also talks about how other methods besides zoom can be utilized as long as the following criterion is met: "text must be resizable without assistive technology up to 200 percent." – haltersweb Jan 12 '16 at 22:35
  • 1
    There are always cases where disabling the zoom makes perfect sense. In a web app brought up by a native app for example, you wouldn't want your customers to be able to zoom. – chazthetic Jan 29 '16 at 03:47
  • I've just built an image zoomer on a page that contains no text; overriding the default zoom to provide enhanced zoom functionality seems like a perfectly good time to disable the browser's pinch zoom. – Conan Oct 19 '16 at 14:18
  • 2
    This is not an answer. Furthermore one may disable native zoom and reimplement it programmatically preserving or even improving accessibiIity – Paolo Dec 12 '16 at 12:53
  • The workarounds, solve half the issue, but still aren't 100% indestructible, imo it would make sense to have a browser option like to "disable javascript" if said people choose to do so. clients! – Paddy Dec 20 '16 at 03:30
-4

This one should be working on iphone etc.

<meta name="viewport" content="width=device-width, initial-scale=1 initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
Cihan Zengin
  • 103
  • 2
  • 12