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

Commit

Permalink
added a warning about restricting zoom via content attribute
Browse files Browse the repository at this point in the history 
fixes #602
  • Loading branch information
@stevefaulkner
stevefaulkner committed Oct 3, 2016
1 parent 755136d commit 29b8934
Showing 1 changed file with 13 additions and 0 deletions.
13 changes: 13 additions & 0 deletions sections/semantics-document-metadata.include
View file
Original file line number Diff line number Diff line change
Expand Up @@ -820,6 +820,19 @@
The <dfn element-attr for="meta"><code>content</code></dfn> attribute gives the value of the
document metadata or pragma directive when the element is used for those purposes. The allowed
values depend on the exact context, as described in subsequent sections of this specification.

<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

This comment has been minimized.

Sign in to view

Copy link
@handcoding

handcoding Oct 3, 2016

Just a teensy suggested change:
users ability → users’ ability

This comment has been minimized.

Sign in to view

Copy link
@chaals

chaals Oct 3, 2016

Collaborator

This is only with name="viewport, right? Not that there are other cases I know of where people might use that content, but this change is only relevant to that particular name value, no?
that is legible for their needs.</p>

<p>The use of these values could be appropriate in specific use cases, for map applications where

This comment has been minimized.

Sign in to view

Copy link
@tagawa

tagawa Oct 3, 2016

Suggestion:
for map applications → for example in map applications
zooming is handled via scripting or for a game application where a fixed viewport is required.

This comment has been minimized.

Sign in to view

Copy link
@chaals

chaals Oct 3, 2016

Collaborator

The case of wanting a fixed viewport for gaming seems weak. Many applications claim to require a fixed viewport, but in fact users sometimes need to trade the functionality of everything in view, in order to get the functionality of "see what I want to look at".
In general their use will not be appropriate and therefore HTML conformance checking tools should

This comment has been minimized.

Sign in to view

Copy link
@tagawa

tagawa Oct 3, 2016

Suggestion:
In general their use → In general, however, their use
display a warning.</p>

</div>

If a <{meta}> element has a <dfn element-attr for="meta"><code>name</code></dfn>
attribute, it sets document metadata. Document metadata is expressed in terms of name-value pairs,
Expand Down

4 comments on commit 29b8934

@anupkumarmaharjan
Copy link

Choose a reason for hiding this comment

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

Displaying warning is not good and not appropriate right now. As there are Tons of projects with meta content with value user-scalable=no are running now.

@chaals
Copy link
Collaborator

@chaals chaals commented on 29b8934 Oct 4, 2016

Choose a reason for hiding this comment

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

@anupkumarmaharjan The problem is that many of these projects are actually making it impossible for users to use them. The point of the warning is to make it clearer that there is a problem using this markup, so hopefully the majority of projects - who are using it unnecessarily, and harmfully - will stop doing that.

@stevefaulkner
Copy link
Contributor Author

Choose a reason for hiding this comment

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

thanks all, updated in response to feedback c6b0011

@trusktr
Copy link

Choose a reason for hiding this comment

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

The problem is that many of these projects are actually making it impossible for users to use them

That's their problem, not yours. Let them figure out who their application is for.

Please sign in to comment.