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

Tweak viewport meta warning #607

Merged
merged 1 commit into from Oct 4, 2016
Merged

Tweak viewport meta warning #607

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
20 changes: 12 additions & 8 deletions sections/semantics-document-metadata.include
View file
Open in desktop
Expand Up @@ -823,9 +823,11 @@

<div class="warning">

<p>Developers should not use the <code>user-scalable=no</code> or <code>maximum-scale=1.0</code>
values in the <code>content</code> attribute as their use hinders users' ability to zoom the
content to a size that is legible for their needs.</p>
<p><a href="https://www.w3.org/TR/css-device-adapt-1/#viewport-meta"><code>&lt;meta name="viewport" content="..."></code></a>
Copy link
Contributor

Choose a reason for hiding this comment

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

This deletion removes the normative "should not" needs to be worked into updated prose.

allows authors to define specific viewport characteristics (such as the layout viewport's width and zoom factor)
for their documents. Among these is the ability to prevent or restrict users from being able to zoom, using
<code>content</code> values such as <code>user-scalable=no</code> or <code>maximum-scale=1.0</code>. Authors should not suppress
or limit the ability of users to resize a document, as this causes accessibility and usability issues.</p>

<div class="example">
The following examples illustrate code that should be avoided:
Expand All @@ -839,11 +841,13 @@
</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 however, their use will not be appropriate and HTML conformance checking tools should
display a warning if developers use these values.</p>

<p>There may be specific use cases where preventing users from zooming may be appropriate, such as map applications –
where custom zoom functionality is handled via scripting.
However, in general this practice should be avoided, and HTML conformance checking tools should display a warning if
they encounter these values.</p>

Copy link
Collaborator

Choose a reason for hiding this comment

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

What I said before. Design for a fixed viewport is too broad a statement IMHO.

Where there is a zoom mechanism, handled by the application - as in the map example - there is a clear use case. Can you explain the game case more clearly?

Copy link
Member Author

Choose a reason for hiding this comment

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

dropped that bit, as i agree. it's not EASY, but games CAN be made to work when zoomed

<p>Note that most user agents now allow users to always zoom, regardless of any
<code>&lt;meta name="viewport" content="..."></code> restrictions – either by default, or as a setting/option (which may however not be immediately apparent to users).</p>
</div>

If a <{meta}> element has a <dfn element-attr for="meta"><code>name</code></dfn>
Expand Down