W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

[manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs

From: Marcos Caceres <w3c@marcosc.com>
Date: Fri, 25 May 2012 15:42:55 +0100
To: Anant Narayanan <anant@mozilla.com>
Cc: public-webapps@w3.org
Message-ID: <479BCEB87079418CA9971EFE1D4A9E82@marcosc.com>

On Sunday, May 13, 2012 at 5:47 PM, Anant Narayanan wrote:

> > > screen_size: This object may contain the min_height and min_width properties that describe the minimum height and width (in pixels) the application needs in order to render correctly. Interpretation of these values is left up to the runtime and/or app store.
> > 
> > 
> > 
> > How does this play with CSS and media queries in particular? What's the use case?
> These values do not interfere with runtime detection via media queries.
> The use case for these values is two-fold:
> - An app store may prevent the user from installing an app on a device
> which doesn't meet this criteria
> - A UA may prevent the user from launching an app on a device which
> doesn't meet this criteria
> The primary goal in both cases is to let the developer declare what
> screen sizes their app is known to work correctly.

The above cases seems very "anti-web" IMHO. I thought we had stopped the whole designing for particular screen sizes, etc. a long time ago. I feel it would be a shame to codify this in a spec.

Marcos Caceres
Received on Friday, 25 May 2012 14:45:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:34 UTC