W3C don't validate Viewport

html w3c w3c-validation
DIDIx13 picture DIDIx13 · Apr 16, 2018 · Viewed 10k times · Source

W3C don't validate my viewport meta tag any idea why?

<title>DIDIx13</title>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no" /> 
<!-- Throws a warning "Consider avoiding viewport values that prevent users from resizing documents." -->
<meta name="keywords" content="DIDIx13" >
<meta name="description" content="I'm Darwin and welcome to my website" >

Answer

DIDIx13 picture DIDIx13 · Apr 16, 2018

TL;DR

Remove "user-scalable=no" and now the validator is fully ok!

I've found out the purpose of "user-scalable=no", thanks to this answer.

Actually "user-scalable=no" prevents the user from zooming. And it allows the browser to gain 300ms per click.

300ms per click? That's pretty damn good! I should let "user-scalable=no"

But this is no longer the case, according to efheng's answer.

<meta name="viewport" content="width=device-width"> is enough to remove 300ms delay.

Related questions

There is no attribute "allowtransparency"

I am looking for some alternate way to do: <iframe transparency=true ... When I do the W3C validation, I am getting the error: Column 31: there is no attribute "allowtransparency" If use this CSS, .iframe-trans-fix{ opacity: 0; filter:alpha(opacity=0); } …

Read More
Can a td be inside a td

It may be a nonsense question, and I know we have to follow standards as much as possible. But can <td> be a direct child of another <td>, like this: <td class="parent"> <…

Read More
W3C validation with AngularJS directives

How do we go about doing W3C validation with an Angular application? Since custom directives make for invalid HTML validation, we typically see lots of W3C validation errors. Are there any strategies for this?

Read More