Are you certain it's a bug?
Are you sure this is not an issue in noVNC?
Is there an existing issue for this?
Issue description
I've connected to the same server using the noVNC web client works correctly, but something in react-vnc's integration can not work.
Please check it