2009-06-03 Pavel Feldman <pfeldman@chromium.org>
Reviewed by Timothy Hatcher.
Enabling debugger requires that Scripts panel is already attached to the
render tree. The reason is that recompile events result in script sources
being added into the source frames. Prior to the global options introduced,
debugger was enabled from the Scripts panel, so that it was guaranteed to
exist. The InspectorController::enableDebugger API calls with no inspector
frontend showing were failing though.
https://bugs.webkit.org/show_bug.cgi?id=26145
* WebCore.base.exp:
* inspector/InspectorController.cpp:
(WebCore::InspectorController::setWindowVisible):
(WebCore::InspectorController::scriptObjectReady):
(WebCore::InspectorController::enableDebuggerFromFrontend):
(WebCore::InspectorController::enableDebugger):
* inspector/InspectorController.h:
* inspector/InspectorController.idl:
* inspector/InspectorFrontend.cpp:
(WebCore::InspectorFrontend::attachDebuggerWhenShown):
* inspector/InspectorFrontend.h:
* inspector/front-end/ScriptsPanel.js:
(WebInspector.ScriptsPanel.prototype.show):
(WebInspector.ScriptsPanel.prototype.attachDebuggerWhenShown):
* inspector/front-end/inspector.js:
(WebInspector.attachDebuggerWhenShown):
git-svn-id: http://svn.webkit.org/repository/webkit/trunk@44398 268f45cc-cd09-0410-ab3c-d52691b4dbfc
10 files changed
