Re: [push-api] Binary messages and use of `USVString` in `PushMessageDataInit` (#159)

Strings aren't encoded...  Though yes, I'm OK with limiting the supported encodings to UTF-8 (that keeps things simple, as well as preventing charset use from being encouraged).

I have no problem accepting a string (probably `DOMString`) for `PushMessageDataInit`, though we would require that it first be encoded using UTF-8 before continuing.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/159#issuecomment-133480516