Bug 181025 – console.log doesn't print anything on JS console of clean machine

• Status: RESOLVED
• Resolution: WORKSFORME
• Component: Web Inspector

[Ebrahim Byagowi]

Repro:
1. Provide a clean or maybe also on recently update macOS.
2. Open JS console using this particular way, right click on the page, click on "Inspect Element", go to "Console" tab.
3. console.log("Hello");

Actual:
Nothing will be printed

Expected:
To console.log work regardless.


It seems for making JS console.log I should enter JS console, particularly using Develop > "Show JavaScript Console", but if I bring it first using "Inspect Element" the bit activates JS console won't be altered.

[Joseph Pecoraro]

This seems like a regression. We should look into this!

[Radar WebKit Bug Importer]

<rdar://problem/36165180>

[Joseph Pecoraro]

Does this reproduce for you with the Safari Technology Preview?

[Ebrahim Byagowi]

> Does this reproduce for you with the Safari Technology Preview?

I can't say for sure as I am not sure whether I've opened console of it on some other way or not. I remember that was happening before update of 10.13 also, can you have a look how logging of JS console will be enabled on Safari? And whether that has anything to do enabling logging or does it change level of visible logs?

[Ebrahim Byagowi]

> And whether that has anything to do [...]

Whether it has anything to do with "Show JavaScript Console" button or not

[Joseph Pecoraro]

I was unable to reproduce this issue. The Console tab shows, the "All" filter is selected, and the log message shows up.

Do you remember what this looked like? If you apply a filter (clicking "Errors" in the Console tab near the top) is that what it looked like? I'm wondering if a filter was applied and you weren't aware. That would indicate we should try to make filters / filtering behavior clearer when applying, but first I'd want to verify if it might have been filters.

[Ebrahim Byagowi]

> I was unable to reproduce this issue.

So you used an unused macOS for that and that happened? So perhaps something is wrong on my side.

> The Console tab shows, the "All" filter is selected, and the log message shows up. Do you remember what this looked like?

I am not sure but can you do some code inspection whether "Show Web Inspector" button has anything to do with console logging level?

> If you apply a filter (clicking "Errors" in the Console tab near the top) is that what it looked like? I'm wondering if a filter was applied and you weren't aware.

I just got familiar with the feature recently and to be honest something never learnt and used throughout many years of consistent use of inspector on Chrome and Safari. but yeah I believe it needs some revamp, perhaps by looking at Chrome and Firefox inspectors.

[Ebrahim Byagowi]

> I was unable to reproduce this issue.

So you used an unused macOS for that and that happened? So perhaps something is wrong on my side.

> The Console tab shows, the "All" filter is selected, and the log message shows up. Do you remember what this looked like?

I am not sure but can you do some code inspection whether "Show Web Inspector" button has anything to do with console logging level?

> If you apply a filter (clicking "Errors" in the Console tab near the top) is that what it looked like? I'm wondering if a filter was applied and you weren't aware.

I just got familiar with the feature recently and to be honest something never learnt and used throughout many years of consistent use of inspector on Chrome and Safari. but yeah I believe it needs some revamp, perhaps by looking at Chrome and Firefox inspectors.

[Blaze Burg]

(In reply to Ebrahim Byagowi from comment #8)
> > I was unable to reproduce this issue.
> 
> So you used an unused macOS for that and that happened? So perhaps something
> is wrong on my side.
> 
> > The Console tab shows, the "All" filter is selected, and the log message shows up. Do you remember what this looked like?
> 
> I am not sure but can you do some code inspection whether "Show Web
> Inspector" button has anything to do with console logging level?

It doesn't. Console messages are buffered regardless of whether a frontend is attached. You need to enable developer tools, though, to buffer messages prior to opening the debugger.

> 
> > If you apply a filter (clicking "Errors" in the Console tab near the top) is that what it looked like? I'm wondering if a filter was applied and you weren't aware.
> 
> I just got familiar with the feature recently and to be honest something
> never learnt and used throughout many years of consistent use of inspector
> on Chrome and Safari. but yeah I believe it needs some revamp, perhaps by
> looking at Chrome and Firefox inspectors.

[Ebrahim Byagowi]

Thanks, I will try to aggregate more things times.

I just guess however "You need to enable developer tools, though, to buffer messages prior to opening the debugger" is going to get forget somehow on system updates and just doing "Show Web Inspector" (and not opening it with inspect) is going to enable it. I wish I could see the code behind it as I am almost sure this happened for me twice on macOS updates.