Re: [w3c/manifest] Support window preferred/initial (minimal?) sizes (#436)

One idea that I've had on this topic is to use the document's <html> tag's size and size constraints as PWA Window size constraints.

i.e

```CSS
html {
  min-width: 300px;
  min-height: 400px;
  max-height: 900px;
}
```

would apply to the PWA Window too.

We'd still probably need a manifest fallback for first run and initial size, but this allows PWAs to dynamically apply different size constraints e.g a Mail App might want a different min-size for a Compose View vs a List View. Crazier still, a site might want to animate the window size through CSS e.g clicking on an item in the List View changes the window size via a CSS transition to expand a Content View.

I'm sure there are issues here (e.g content size or window size? maybe use box-sizing property?), but the core point is that the CSS engine has powerful box sizing primitives, and it would be cool to let PWAs express the behavior of their 'box' through these existing semantics.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/436#issuecomment-533428290

Received on Friday, 20 September 2019 06:39:32 UTC