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

I’m not averse to a simple approach to this (like what @mgiuca mentioned) with the caveat that browsers should retain the user’s preference if they’ve resized the window on their own.

I do see some use for this in the [screen enumeration](https://github.com/spark008/screen-enumeration) and [window placement](https://github.com/spark008/window-placement) scenarios we discussed at TPAC yesterday (e.g. financial dashboards), but those are far more complex, with multiple windows to control and arrange with respect to one another. I like the idea of declaratively establishing the organization of multiple windows (or even one), but I think I’d prefer to create some sort of external definition (similar to `ImageResource`) that could be pulled into a manifest rather than have it be defined in the manifest spec itself.

Syntax wise, it could be something like this:

```json
"windows": [{
  "name": "foo",
  "size": "640x480",
  "position": { "x": "100", "y": "100" }
},
{
  "name": "bar",
  "url": "/tools/panel.html",
  "size": "640x480",
  "position": { "x": "100", "y": "100" }
}]
```

On opening an app for the first time, it could loop through the windows and generate and place each one. Without a `url` property, the `start_url` would be used. URLs would need to be in scope (naturally) and `name` (which might be optional) could be used for cross-window communication. We could also extend `position` to include `z` for spacial apps.

-- 
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-533386165