Copyright © 2011 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
The public is encouraged to send comments to the WebApps Working Group's public mailing list public-webapps@w3.org (archive) by the 15 September 2011. See W3C mailing list and archive usage guidelines. Advisory Committee Representatives should consult their questionnaires.
No substantive changes were made as a result of the Candidate Recommendation phase (see also diff and implementation report). Advance of this specification to Recommendation is blocked until the Media Queries specification (a normative reference for this specification) advances to Recommendation.
This document was published by the Web Applications WG as a Proposed Recommendation. This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to public-webapps@w3.org (subscribe, archives). All feedback is welcome.
Publication as a Proposed Recommendation does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
This section is non-normative.
Web applications, be they widgets or in-browser, can on most platforms be run in multiple visual modes. At times they may occupy the entire screen, at others they may be minimized to a specific docking area; at times they may have chrome that matches the operating system's style while at others they may be providing their own controls in order to provide for a more immersive experience.
The user is generally in control of at least several aspects of these modalities, and it is therefore important for authors to be able to react to these in order to provide different styling to their applications. In order to achieve this, this specification defines a media feature that allows different CSS style rules to be applied depending on whether a given media query [MEDIAQ] matches.
This section is non-normative.
The design goals and requirements for this specification are documented in the Widgets 1.0 Requirements [WIDGETS-REQS] document.
This document addresses one requirement from "User Experience":
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.
The key words must, must not, required, should, should not, recommended, may, and optional in this specification are to be interpreted as described in [RFC2119].
This specification defines conformance criteria that apply to a single product: user agents that implement the view modes that it contains.
An application could be designed to trick users into performing actions they do not wish to or to capture data that they did not intend to provide. Examples of situations in which the user could be tricked include, but are not limited to:
Implementers are encouraged to take these issues into consideration and to provide limitations to what a Web application may do in order to ensure that the user is exposed to minimal risk.
'view-mode'
media featureThe view-mode media feature describes the mode in which the Web application is being shown as a running application on the platform.
A user agent should make a best-effort attempt at matching the great variety of platform conventions in which it may be running a Web application to the list of view modes defined in this specification so that the view-mode media feature may describe common situations in a manner that is useful to authors. Each view mode is defined to be exclusive of the others.
The view-mode media feature accepts the following enumerated values:
A simple example in CSS:
@media handheld and (view-mode: floating) and (orientation: landscape) { // ... } @media tv and (view-mode: windowed) { // ... } @media handheld and (view-mode: fullscreen) { // ... }
This section is non-normative.
Daniel Herzog, Arve Bersvendsen, Arthur Barstow, Jochen Cichon, Sebastian Markbåge, Cameron McCormack, David Rogers, Richard Tibbett, Scott Wilson, Boris Zbarsky, Kenneth Christiansen, Daniel Glazman, Tab Atkins Jr, Josh Soresh, Marcin Hanclik, the CSS WG.