These are chat archives for opal/opal

26th
Apr 2018
G. Gibson
@mistergibson
Apr 26 2018 16:31
Anyone else had issues with Chrome ver. 66? It breaks my code
Firefox, Opera both work fine
eiko
@eiko
Apr 26 2018 16:35
@mistergibson i haven't experienced anything yet, but my code is simple at this point. are you getting a specific error?
G. Gibson
@mistergibson
Apr 26 2018 16:35
no, but it is as if it refuses to actually execute selected chunks of JS
Also, it does some strange things with my websocket connect attempts
it converses for a while, but refuses to complete the 'conversation' with my server code
other browsers don't do that and work perfectly
odd behavior that
Note: version 64 worked perfectly
eiko
@eiko
Apr 26 2018 18:02
are you running this setup locally? or do you have an actual remote server? i know chrome 65 introduced a lot of strict cross-origin policies that would break any code running from a different domain than the client
G. Gibson
@mistergibson
Apr 26 2018 18:03
testing on localhost:3000
the websocket does get established - but the conversation gets whacked in 66
I'm not pulling any cross-domain hoo-hah though
eiko
@eiko
Apr 26 2018 18:16
interesting. i'll poke around with 66 when i have time to see if i can replicate it.
G. Gibson
@mistergibson
Apr 26 2018 18:22
cool, thanks
G. Gibson
@mistergibson
Apr 26 2018 21:56
they pushed an update to 66 today - no change, still borks