151714 2015-12-01 12:28:39 -0800 When Debug UI is enabled, Inspecting the Inspector should always be available 2026-01-12 09:05:43 -0800 1 1 1 Unclassified WebKit Web Inspector WebKit Nightly Build Unspecified Unspecified NEW InRadar P2 Normal --- 147066 1 bburg webkit-unassigned graouts inspector-bugzilla-changes webkit-bug-importer oldest_to_newest 1145327 0 bburg 2015-12-01 12:28:39 -0800 NOTES: We currently require some extra steps to enable 2nd-level inspector. It's currently guarded by two different NSUserDefaults (http://trac.webkit.org/wiki/WebInspectorDebugging#InspectingtheInspector). It has been proposed elsewhere that we add a separate DebugUI button for inspecting the inspector. I would like a shortcut too, Cmd-Shift-Opt-I (Cmd-Shift-Opt matches other DebugUI shortcuts). 1145328 1 bburg 2015-12-01 12:28:56 -0800 Internally filed at <rdar://problem/12628083> 1148833 2 bburg 2015-12-13 12:38:48 -0800 the "Inspect Element" context menu item is added inside WebCore code. It checks InspectorController::enabled(), which calls to developerExtrasEnabled(), which in the Web case, is tied to PageSettings::developerExtrasEnabled(). The second-level inspector has a separate page group. To make 2nd-level inspector always available, we can always add the context menu in engineering builds only if the inspection level is >0. 1148837 3 bburg 2015-12-13 13:02:03 -0800 (In reply to comment #2) > > To make 2nd-level inspector always available, we can always add the context > menu in engineering builds only if the inspection level is >0. It would be even better if we can execute some injected script if inspectionLevel() > 0 to see if debug UI is enabled. We'd need to evaluate the following from InspectorController (in the context of the main frame's document). !!(WebInspector && WebInspector.debugUIEnabled()) How can we evaluate something like this in the main frame's ExecState?