Hi Pat,

Are you still seeing this issue? We also experienced this problem when we updated to version 52, but it inexplicably went away after a few hours, so we’re guessing Chrome changed something.

Thanks!
Amy

Still an issue for me. What version are you running?

Sorry Pat, I spoke too soon. It looks like something with Salesforce and Chrome is breaking the console. I’m on version 52.0.2743.8252 of Chrome and can’t do any commands in console if I have a Salesforce header/footer or even just a Chatter component on my page. If I have just Skuid components I’m getting functionality back, though.

Thanks!
Amy

Confirmed as well. Without Chatter or header/sidebar everything seems to work fine.

Skuid and Salesforce conflict then. Hmmm… 

Wow, this is frustrating! I didn’t realize how much I rely on the console until I couldn’t use it.

My version says 52.0.2743.82 m (64-bit)

Okay, thanks, and it looks like it’s a Chrome issue because the console does work in Firefox

Why would it only break when the salesforce header/sidebar is on?

Yeah. I forgot to mention that.

So it’s when Salesforce Header/sidebar/chatter feed and Chrome are used.

I think it’s because the problems are coming in with Salesforce and Chrome rather than Skuid and Chrome. For instance, I can’t use my console on standard Salesforce pages. Are you able to use the Chrome console on standard Salesforce pages?

Confirmed bug in Chrome 52. See: https://bugs.chromium.org/p/chromium/issues/detail?id=632305
   
This is fixed in Chrome 53, slated for September release in the general channel.

EDIT:

For developers I highly recommend setting yourselves up with Chrome Canary:

https://www.google.com/chrome/browser/canary.html 

I can confirm this bug is fixed and the console works as expected this posting in “54.0.2811.0 canary (64-bit)”