Gracefully handle non-JSON postMessages

I came across this when using a browserified version of node's process.nextTick which uses postMessage to trigger an efficient equivalent to setTimeout(0)

In this case the event data is "process-tick" or similar which throws an exception in xdomain. I think it would be better if xdomain just ignored the message if it can't parse it as JSON