You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly, I've been using cljs-devtools for a number of years now, it's brilliant and has saved me a lot of time and effort, so thank you to all involved in its production.
Up until recently, I always had an option when right-clicking on a JS object (including any CLJS instance) in the console to "Store as Global Variable". However more recently, sometimes the option appears but more often than not, it just isn't available at all. The only thing that is available is "Show as JavaScript object". I've checked all the Chrome options and haven't spotted anything at all that could be responsible for this.
Has anyone else come across this issue, or do you know if there is some workaround available? I'm fairly sure it's a Chrome issue and not a cljs-devtools issue, but I thought I'd post here since I couldn't find anything else in any Chrome forum across the web that might be able to explain this.
Thanks
The text was updated successfully, but these errors were encountered:
Firstly, I've been using cljs-devtools for a number of years now, it's brilliant and has saved me a lot of time and effort, so thank you to all involved in its production.
Up until recently, I always had an option when right-clicking on a JS object (including any CLJS instance) in the console to "Store as Global Variable". However more recently, sometimes the option appears but more often than not, it just isn't available at all. The only thing that is available is "Show as JavaScript object". I've checked all the Chrome options and haven't spotted anything at all that could be responsible for this.
Has anyone else come across this issue, or do you know if there is some workaround available? I'm fairly sure it's a Chrome issue and not a cljs-devtools issue, but I thought I'd post here since I couldn't find anything else in any Chrome forum across the web that might be able to explain this.
Thanks
The text was updated successfully, but these errors were encountered: