RESOLVED WORKSFORME Bug 158951
Web Inspector completely empty 
https://bugs.webkit.org/show_bug.cgi?id=158951
Summary Web Inspector completely empty
lepolt
Reported 2016-06-20 12:25:47 PDT
Created attachment 281661 [details] Empty inspector All tabs are completely empty and never update with data. Have tried restarting Safari, but the Web Inspector is non-responsive. I've been trying to use the Safari Web Inspector in place of the Chrome dev tools, but so far it has been a less than pleasant experience.
Attachments
Empty inspector (29.60 KB, image/png)
2016-06-20 12:25 PDT, lepolt 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2016-06-20 12:33:51 PDT
<rdar://problem/26898705>
Joseph Pecoraro
Comment 2 2016-06-20 13:06:20 PDT
Can you clarify what revision of WebKit / Safari this was? System Safari, WebKit Nightly, Safari Technology Preview?
lepolt
Comment 3 2016-06-27 04:02:43 PDT
Safari 9.1.1 (11601.6.17)
Joseph Pecoraro
Comment 4 2016-06-27 12:12:20 PDT
• Does the issue reproduce on every page? • Does the issue reproduce for you in WebKit Nightly or Safari Technology Preview? I highly suspect you are running into some kind of uncaught exception in the inspector frontend. There are some steps you can run to provide us with more information. Would you be willing? (The steps are mostly on <https://wiki.webkit.org/wiki/WebInspectorDebugging>).
Joseph Pecoraro
Comment 5 2016-06-27 12:14:19 PDT
Namely, I think you can enable these defaults and restart Safari. defaults write com.apple.Safari "com.apple.Safari.ContentGroupPageIdentifier.WebKit2LogsPageMessagesToSystemConsoleEnabled" -bool YES defaults write com.apple.Safari WebKitLogsPageMessagesToSystemConsoleEnabled -bool YES defaults write com.apple.Safari WebKitDebugLogsPageMessagesToSystemConsoleEnabled -bool YES And then check syslog (Console.app) for some output. You can then do -bool NO and restart Safari to disable the logs.
Blaze Burg
Comment 6 2017-02-10 20:26:34 PST
We lack insufficient information to proceed with this bug. Please reopen if you are able to provide Joe with some more information.
Note You need to log in before you can comment on or make changes to this bug.