Websites Prep for Google’s ‘Mobilegeddon’

Re:Websites Prep for Google’s ‘Mobilegeddon’ by xyby on Tuesday April 21, 2015 @12:38PM (#9415242)

According to your first link, there is no reason to disable zoom. This gives you the best of both worlds:

    <meta name="viewport" content="width=device-width">

It retains zoom and gets rid of the 300ms delay. At least in chrome, so the site says.

FF says this issue is "RESOLVED FIXED", so maybe they implemented it too:

https://bugzilla.mozilla.org/show_bug.cgi?id=941995

I have that meta tag on all my sites and I just tested on Android and iOS: Clicking on links and other controls seem instant. And zoom works. Hurray!

[ Parent | on HN ]

Re:Websites Prep for Google’s ‘Mobilegeddon’ by leephillips on Tuesday April 21, 2015 @01:20PM (#9415539)

    "<meta name="viewport" content="width=device-width">"

Which is just what I do. Disabling zoom is one of those nonsensical practices that spreads as web "developers" copy code from each other. I suppose there's a use case for it somewhere, but its main purpose is to remove choice and make sites harder to use.

EDIT: Actually I also include the initial-scale as in the comment below.

[ Parent | on HN ]

Re:Websites Prep for Google’s ‘Mobilegeddon’ by Shorel on Tuesday April 21, 2015 @01:50PM (#9415751)

I have

    		<meta name="viewport" content="width=device-width, initial-scale=1.0">

[ Parent | on HN ]

Re:Websites Prep for Google’s ‘Mobilegeddon’ by Steuard on Tuesday April 21, 2015 @11:23PM (#9418509)

Huh. I only have the initial-scale entry, and I think that my sites always show up with page width matching device width as a result. Is there something important that the extra width specification does that I'm missing?

[ Parent | on HN ]

Re:Websites Prep for Google’s ‘Mobilegeddon’ by leeoniya on Tuesday April 21, 2015 @01:35PM (#9415647)

ah excellent, went ahead and updated my properties :)

[ Parent | on HN ]