No current plans to pursue this.

No longer reproduces.

No longer valid as far as I can find.

ehhh, not sure about this. It's not worse, like I can pinch to zoom in Safari, but not Chrome.

Rolling, so we'll see how accurate the simulator was.

I am just intrigued that user-scalable=no actually means "somewhat user-scalable".

No, I hate all zooming.

(I am glad to see the auto-zoom-on-controls gone and don't care about any other zoom feature.)

Right. Do you use that?

Oh -- but double-tap-to-zoom doesn't? 😕

I tested pinch to zoom, which still works. We just turn off the auto-zoom. I'll roll the server here and give a more thorough shakedown.

(Specifically, D17714 added user-scalable=no, which probably does the opposite of what this requested.)

Removed.

Hopefully Android browsers will hurry up and ignore that tag too..

There are at least some nontrivial effects, like searching for text without "maximum-scale" can imply a zoom:

I have an idea for this.

I'll probably build a conpherence package, but overall this is likely as good as it gets. I don't think there will be any additional benefit without building a full separate mobile app.

The first page I found on the internet claims the iPhone 7 will be 1920x1080, so my strategy looks like it's paying off!

@epriestley Missed a spot: D16325

D16323 uses <input type="text" pattern="\d*" />, which appears to have the best behavior.

On iOS 9.2 in the simulator, <input type="number" /> gives you this keyboard:

Oh, there's a "Toggle Software Keyboard" option that I somehow disabled.

On iPhone Simulator, the behavior of <input type="number" /> appears to be "draw the keyboard for 1 frame and then immediately hide it".

Looks like an iPhone with Gboard keyboard.

Offhand, do you know if <input type="number" /> has the desired behavior on your device?

thanks, I couldn't seem to find it.