[w3c/push-api] Should there be a UTF-8 health warning? (#335)

 PushMessageData interface 
https://www.w3.org/TR/push-api/#pushmessagedata-interface

In w3c/push-api#276 we asked about the inherent UTF-8 requirement for the `text` (and to a far lesser extent `json`) methods. These method's default implementation assumes that the encoding of the message's bytes are, in fact, UTF-8 if the message is to be treated as text. The I18N WG is happy that UTF-8 is the default encoding and that it is the *only* supported encoding. But we note that there is no mention outside of the message data interface of UTF-8 or Unicode. Other data can be sent down the wire and retrieved using `arrayBuffer` or `blob`, but there is no mention of character encodings aside from the references to `utf-8 decode` and `utf-8 encode` in this section. So our ask is:

Should there be a health warning about using non-UTF-8 encodings?

[Note: this came out of I18N WG reviewing our previous comments in our periodic review cycle]

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/335