- From: L. David Baron <notifications@github.com>
- Date: Sat, 21 Jul 2018 16:52:15 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 21 July 2018 23:52:38 UTC
OK, I had a look at the correct version this time. I filed three pull requests (see above), and also have a few comments: 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. Two of the comments in https://github.com/w3ctag/design-reviews/issues/221#issuecomment-400143812 still seem to apply: > * 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 <ins>in the future</ins> files. <strike>Right now that's [stated in the example section](https://wicg.github.io/web-share-target/#usage-example) but</strike> the [relevant normative part of the spec](https://wicg.github.io/web-share-target/#sharetarget-and-its-members) seems to assume the reader knows what "the title", "the text", etc., are. and (for both specs): > * I wonder if there should be some way for associating MIME types with the files. Otherwise things look good to me, at least after one read-through. -- 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-406830642
Received on Saturday, 21 July 2018 23:52:38 UTC