- From: Matt Giuca <notifications@github.com>
- Date: Mon, 19 Jun 2017 18:02:55 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 20 June 2017 01:03:28 UTC
Hi again, Just a note that we've added some new logic to the draft spec (this functionality is in Chrome's implementation but wasn't previously in the spec draft due to an oversight): https://wicg.github.io/web-share/#share-method Three new steps have been added to the `share` algorithm (Steps 2, 3 and 4). What this amounts to is that the `url` field is processed as a URL relative to the current document, with three practical effects: - If `url` is invalid, `share` rejects with a `TypeError`. - If `url` is relative, it is resolved with respect to the current document URL. - `url` is normalized into ASCII with UTF-8 percent encoding. Discussion [here](https://github.com/WICG/web-share/pull/35). Please let me know if you think this change is bad (if the `url` field should actually just be treated as a string) or whether this needs a new TAG review. Thanks. -- 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/179#issuecomment-309614628
Received on Tuesday, 20 June 2017 01:03:28 UTC