Re: [w3c/manifest] Abstracting selecting an icon. (#710)

The "adaptive icon PR" @kenchris mentions is #657. I don't think this clashes with that. `ImageResource` isn't being extended there, we're just adding a new "purpose".

@jakearchibald Will Service Worker be making use of the `ImageResource` dictionary defined here? Including "purpose" and "platform"? Otherwise it might not make sense to do this, as Marcos says.

@marcoscaceres Why is WebIDL not appropriate for defining a document format?

It defines a JSON dictionary structure much more succinctly and readably than the parser algorithms we had previously specified. I don't think there's a problem with using the same definition for both interfaces and JSON. Even if it doesn't make sense in service workers to re-use `ImageResource`, imagine a hypothetical API where you can dynamically register new icons for the manifest:

```webidl
void RegisterIcon(ImageResource icon);
```

It would make sense to re-use `ImageResource` dictionary for that method, no?

-- 
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/pull/710#issuecomment-414913995