Use JSON to pass messages instead of plaintext?

[al-the-x]

Use JSON to pass messages instead of plaintext?

[onyxfish]

Hi David, thanks for the suggestion. The reason we aren't passing JSON is that using JSON over postMessage is not supported by older browsers, including IE9. So in order to pass JSON and maintain browser compatibility we would have to a) stringify it and b) add a dependency on json2.js or some other cross-browser JSON parsing library.

This didn't seem worth the trouble, though I'm not surprised to here other libraries aren't being careful about what messages they receive. Happy to hear other suggestions for how me might prevent those sorts of issues!

[al-the-x]

Ah, I understand that rationale. I didn't know about the restriction on
JSON via postMessage in IE<=9, either, so that's valuable...! I wonder
how my other vendor is handling that. -_-

Thanks for the insight!

close #43
​

[onyxfish]

You're very welcome. Thanks for the PM offer.

[hampelm]

At this point, this may be better handled by the message producers and consumers. However, I did want to ask about point (b) adding a json parser since this came up in some debugging today. Would the built-in JSON.parse not be sufficient? caniuse suggests it's supported in IE 9.

In any case, a warning in the readme that only strings are supported might be in order (happy to open that PR)