- From: Marcos Caceres <marcosc@opera.com>
- Date: Tue, 16 Mar 2010 20:01:21 +0100
- To: Robin Berjon <robin@berjon.com>
- Cc: public-webapps WG <public-webapps@w3.org>
Hi Robin, I've not gotten the cycles to finish the review below... However, before it's any later, this spec needs to define when the width and height of a widget can be ignored/used: P&C sez: "7.6.3. The height Attribute A numeric attribute greater than 0 that indicates the preferred viewport height of the instantiated custom start file in CSS pixels [CSS21]. Authoring Guidelines: It is optional for authors to use the height attribute with a widget element. This value is only applicable to particular view modes, meaning that for certain view modes this value is ignored. The view modes that honor the value of the height attribute are defined in the [Widgets-Views] specification." The same goes for width. On Thu, Mar 4, 2010 at 2:13 PM, Robin Berjon <robin@berjon.com> wrote: > Hi all, > > I just produced an update of VMMF to make it ready for publication: http://dev.w3.org/2006/waf/widgets-vmmf/. > > Essentially I changed it so that it corresponds to CSS Media Queries. That, plus it being a UI oriented specification, means that there's only one normative assertion and it's a SHOULD. > > Comments welcome, I think that this baby can ship. > 5. The 'view-mode' media feature > > The view-mode media feature describes the mode in which the widget is > being shown as a running application on the platform. > > Value: > application | floating | fullscreen | maximised | mini | all > Applies to: > visual and tactile media types > Accepts min/max prefixes: > No > > A user agent should make a best-effort attempt at matching the great > variety of platform conventions in which it may be running a widget 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. > 5.1 View modes > > The view-mode media feature accepts the following enumerated values: > > application > Describes a widget is running in an application-like mode, > typically in a windowed manner and with chrome. > floating > Describes a widget providing a more immersive interface, running > in a windowed manner but without chrome, and with viewport's > background being transparent such that other system items such as > other applications or the display's background can be seen through > part of the viewport that are not being painted to. > fullscreen > Describes a widget that is occupying the entirety of the display, > without any of the system chrome being shown (e.g. a fullscreen > video). > maximised > Describes a widget that is occupying the entirety rendering area > that the platform dedicates to applications, which is to say all of > the display minus areas that the platform conventions maintain almost > constantly present (e.g. the menu bar, the clock and similar icons, > the system menu, etc.). > mini > Describes a widget docked or otherwise minimised, but with a > dynamic graphical representation being available nevertheless (i.e. > the widget isn't entirely hidden). This may correspond for instance to > a thumbnail of the widget's content being shown. > all > Describes all of the above cases, and always causes the media > feature to return a true value. > -- Marcos Caceres http://datadriven.com.au
Received on Tuesday, 16 March 2010 19:02:14 UTC