bytes in hex view no more accurate after chrome update

the bytes in hex view are no more accurate after chrome update (73.0.3683...).
e.g.
before update -> after update
04 -> 42 41 3d 3d or
15 00 13 -> 44 77 41 4e

great extension though. I hope there will be an update.

Start by reproducing the incorrect byte values in the extension's hex view with Chrome 73. Compare the reported inputs and outputs, then trace the conversion path to identify where the displayed bytes diverge. Done means the examples and equivalent WebSocket frames show accurate hexadecimal bytes again.

Written by the indexing model from the issue text.