UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36

Steps to reproduce the problem:
The Chrome dev tool's WebSocket inspector does not render binary frames. Instead, it just shows the message as "Binary Frame (Opcode 2, mask)" which isn't actually helpful.

What is the expected behavior?

What went wrong?
I certainly don't expect Chromium to render arbitrary binary data (since it could be an image, proto message, etc.) But ideally I could at least copy the hex-encoded message so I could debug the WebSocket messages.

Did this work before? No 

Chrome version: 49.0.2623.75  Channel: n/a
OS Version: OS X 10.11.3
Flash Version: Shockwave Flash 20.0 r0

This is especially difficult when I'm connecting to minified/compiled JavaScript files and don't have as easy of a time stepping through the source when the WebSocket message is being constructed.