On Fri, Jul 12, 2019 at 9:05 AM Boris Zbarsky <bzbar...@mit.edu> wrote: > You could simplify this a bit by calling > nsContentUtils::ewURIWithDocumentCharset, but that doesn't solve most of > the issue.
>From the name that sounds somewhat wrong to me too. At least, for new APIs I think we should always use UTF-8 as the encoding passed to the URL parser and having now looked up https://wicg.github.io/web-share/#share-method that is also what should happen per the draft (Safari might actually do this wrong then, I recommend adding a test). _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
