Short answer: Yes, it’s possible.
The Debugger (the thing that shows up at the bottom of the browser when “?debug_mode=true” in your URL is present) is kind of sort of ALWAYS console logging for you. It just does that in a very interactive way.
I think you know the first part: If you set a breakpoint, execution will stop. The second part is: when execution stops, you can click through various values and variables and expose their values.
But I feel you… Sometimes just spitting things to the console would be a LOT easier!
You can do that, though:
Caveats: It’s weird how this works. (Actually, I find it slightly weird this works at all.) What happens is that “> Insert dynamic data” things you insert become ACTUAL TEXT in the executed code. So you have to anticipate and string delimit things in your console.log() statement.
ODDLY ENOUGH, I’m actually working with some Toolbox stuff right now and Console Logging the heck out of stuff, so it was easy for me to divert for a moment and give you this example…
So here’s an example for you. In the thing I’m working on at the moment, I pre-load some data on “page is loaded”. I know that that’s all working right, but let’s say that I didn’t.
Here’s how I can write some info to the console:
Note how I string delimited all the stuff I want to show.
At this point you are saying:
“Oh cool. Also, I see the highlights, but WTF is the red pen mark???”
Well, the red pen mark indicates that link I’m gonna click so I can show you the CODE that appears in the page when you do this. This is the part that I think is weird, but this is how it works.
What you’ll see is that this dynamic data just shows up as text in the code of the function we’re running. So when I click the “VM5446:5” link, here’s the code we see:
But hey, there you go… using console.log() with Bubble.