"No Image" introduced issue with websocket rendering on Safari

[hafen]

Here's a video comparing Safari and Chrome. When the websocket server returns a message to the browser saying the image has been rendered, on Safari it goes to "no image" while on Chrome it shows the image. This one will be hard to replicate in a dev environment but maybe there are some clues in the newly-introduced "no image" code that can help figure out what might be going on.

websocket.mp4

[Incin]

This issue is only reproducible in r, a local websocket server it worked fine. We decided to shelf this for now due to the nature of testing and fixing this.