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

I think that this is just in error.  The source here should be a sequence of bytes, because that is what comes in across the wire (even in a protocol that only carries strings, this reduction is possible).  Then, the string variants of the mixin can decode that string using whatever hints available from the underlying protocol, like `charset` parameters.  That might fail.

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