3 ms·
Hmmm. Thanks for reporting. Mixlr uses WebSockets when available (i.e., Chrome) and falls back to Flash, so this error probably means the WebSocket port was blo
by transmit101 16y ago
Hmmm. Thanks for reporting. Mixlr uses WebSockets when available (i.e., Chrome) and falls back to Flash, so this error probably means the WebSocket port was blocked for some reason, maybe a firewall. I agree the error message is a bit skewed in this case. I am going to do some more work to minimize this kind of problem, it's not perfect yet.