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

Section 10 states "`PushMessageData` objects have an associated bytes (a byte sequence) set on creation." Given that—and the `blob()` and `arrayBuffer()` methods—I'm curious why `PushMessageDataInit` uses `USVString` instead of, e.g., `ArrayBuffer`. Does this mean that all decrypted messages must be UTF-8 encoded strings?

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