Skip to content
This repository has been archived by the owner on Jul 30, 2019. It is now read-only.

Commit

Permalink
updated meta warning in response to feedback
Browse files Browse the repository at this point in the history
  • Loading branch information
@stevefaulkner
stevefaulkner committed Oct 4, 2016
1 parent 29b8934 commit c6b0011
Showing 1 changed file with 16 additions and 4 deletions.
20 changes: 16 additions & 4 deletions sections/semantics-document-metadata.include
View file
Original file line number Diff line number Diff line change
Expand Up @@ -824,13 +824,25 @@
<div class="warning">

<p>Developers should not use the <code>user-scalable=no</code> or <code>maximum-scale=1.0</code>
values in the <a>content</a> attribute as their use hinders users ability to zoom the content to a size
values in the <a>content</a> attribute as their use hinders users' ability to zoom the content to a size
that is legible for their needs.</p>

<p>The use of these values could be appropriate in specific use cases, for map applications where
<div class="example">
The following examples illustrate code that should be avoided:
<pre highlight="html">

&alt;!-- DO NOT DO THIS -->

&alt;meta name="viewport" content="<mark>user-scalable=no</mark>">

&alt;meta name="viewport" content="width=device-width, initial-scale=1.0, <mark>maximum-scale=1.0</mark>">
</pre>
</div>

<p>The use of these values could be appropriate in specific use cases, for example in a map application where
zooming is handled via scripting or for a game application where a fixed viewport is required.
In general their use will not be appropriate and therefore HTML conformance checking tools should
display a warning.</p>
In general however, their use will not be appropriate and HTML conformance checking tools should
display a warning if developers use these values.</p>

</div>

Expand Down

3 comments on commit c6b0011

@anupkumarmaharjan
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A suggestion, what if we can make the ability of the user zooming won't effects the whole design flow except all the block will get zoomed up even those which are fixed element with position:fixed;

@chaals
Copy link
Collaborator

@chaals chaals commented on c6b0011 Oct 4, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@anupkumarmaharjan In general we don't try to tell browsers how to make their User Interface work, (except in cases where we do,) and especially not at this level of detail. So I am not sure we would get agreement to do this in the "core" HTML specification.

"Good ways for browsers to behave" sounds like a new project. It might be worth starting from the User Agent Accessibility Guidelines since they do describe things that browsers should do. They don't have much input from developers of applications, unfortunately, and they are not currently under development. But W3C would probably relicense the content to an effort at producing something useful.

@anupkumarmaharjan
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chaals I am in. I would love to help in anyways to develop common browser policy so that all browser would be same in functionality (at least) so that there won't be any hectic in designing websites or web apps.

Please sign in to comment.