- From: Matt Giuca <notifications@github.com>
- Date: Sun, 22 Jul 2018 22:24:01 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 23 July 2018 05:24:47 UTC
> It seems like it might be worth a non-normative note explaining future expansion plans for images/files (and their being POST-only) if that part of the spec isn't going to be written soon, just so it doesn't get forgotten and so somebody else could pick it up later. I agree — we could have a section similar to my [Extensibility of this API](https://wicg.github.io/web-share/#extensibility-of-this-api) section in Web Share, but I got some negative feedback on this in WICG/web-share#61. > It would probably be useful to say what a share consists of. I understand it to be a sort of arbitrary bundle of title, text, url, and in the future files. Right now that's stated in the example section but the relevant normative part of the spec seems to assume the reader knows what "the title", "the text", etc., are. Aren't the descriptions in [`ShareTargetParams` and its members](https://wicg.github.io/web-share-target/#sharetargetparams-and-its-members) enough? > I wonder if there should be some way for associating MIME types with the files. I think that will be relevant when we introduce file sharing, but not for the initial version of the spec which doesn't include file sharing. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/221#issuecomment-406942697
Received on Monday, 23 July 2018 05:24:47 UTC