Bug 211590 – Web Inspector: Unable to Show JavaScript Console in empty tab in Safari Technology Preview

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

[Jeff Johnson]

I'm using Safari Technology Preview Release 105 (Safari 13.2, WebKit 14610.1.10) on macOS 10.14.6. This bug does not occur with Safari Version 13.1 (14609.1.20.111.8) on the same system.

Steps to reproduce:
1) Launch STP
2) Press option-command-c to Show JavaScript Console.

Expected results: Web Inspector opens to Console.

Actual results: Nothing happens.

Notes:
The keyboard shortcut option-command-i to Show Web Inspector *does* work on an empty tab. However, option-command-a to Show Page Resources also fails, along with Show JavaScript Console. Option-command-u to Show Page Source... that crashes reproducibly in -[_WKInspector showMainResourceForFrame:], I just discovered. That could be another bug, I suppose, but I was already filing this one.

I believe this issue is related to https://bugs.webkit.org/show_bug.cgi?id=209628 and https://bugs.webkit.org/show_bug.cgi?id=209639

Bizarrely, if you try option-command-c first, which fails, and then try option-command-i, the Web Inspector opens in a big empty white window the size of the screen.

[Radar WebKit Bug Importer]

<rdar://problem/63000159>

[Simon Fraser (smfr)]

Chris, is this because we haven't fired up a WebContent process yet?

[Chris Dumez]

(In reply to Simon Fraser (smfr) from comment #2)
> Chris, is this because we haven't fired up a WebContent process yet?

Yes, but this is an old issue and this has been fixed in Safari 14 AFAIK. I am unable to reproduce on Safari 14.

[Chris Dumez]

Please verify that this is fixed in Safari 14 (or latest STP).

[Jeff Johnson]

It's not fixed in Safari 14 or STP 116 released today.

Additional step to reproduce:
Preferences, General, New Windows open with Empty Page, New Tabs open with Empty Page.

[Simon Fraser (smfr)]

I can reproduce.

Chris, you have to do "Show JavaScript Console" from the Develop menu without first opening the inspector.

[Chris Dumez]

(In reply to Simon Fraser (smfr) from comment #6)
> I can reproduce.
> 
> Chris, you have to do "Show JavaScript Console" from the Develop menu
> without first opening the inspector.

Oh, I can now too. Maybe I had done something that had launched the process already when I tested earlier. I will investigate.

[Chris Dumez]

Created attachment 414633 [details]
Patch

[EWS]

Committed r270060: <https://trac.webkit.org/changeset/270060>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 414633 [details].