Bug 55923 - Viewport lost "default" keyword, but is it still needed?
Summary: Viewport lost "default" keyword, but is it still needed?
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-07 20:53 PST by Joseph Pecoraro
Modified: 2011-03-07 20:53 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph Pecoraro 2011-03-07 20:53:19 PST
In the past, a valid keyword for viewport value was "default". This would
become the webkit client's default value for the given viewport key, similar
to "auto" when the value is undefined.

I don't think this concept is mentioned in the "css-viewport" spec, but this is a
regression from former behavior and functionality:
http://people.opera.com/rune/TR/css-viewport/

I'm still trying to work out whether or not it needs a new "ValueDefault"
enum value, or if "default" is just a way to explicitly say "ValueAuto".
Also, is this even necessary anymore? It seems as if web content
wants to dynamically change its viewport, it should just set the <meta>
tag again, and that will entirely replace the old viewport settings.