-
ggaren@apple.com authored
https://bugs.webkit.org/show_bug.cgi?id=121194 Reviewed by Joseph Pecoraro. We plan to use the "evaluate" API and debugger activation property access for all the features we need. Source/WebCore: * inspector/JavaScriptCallFrame.idl: These are the interfaces I removed. * bindings/js/JSJavaScriptCallFrameCustom.cpp: * inspector/InjectedScript.cpp: * inspector/InjectedScript.h: * inspector/InjectedScriptSource.js: * inspector/Inspector.json: * inspector/InspectorDebuggerAgent.cpp: (WebCore::InspectorDebuggerAgent::setScriptSource): * inspector/InspectorDebuggerAgent.h: * inspector/JavaScriptCallFrame.idl: * inspector/front-end/RemoteObject.js: (WebInspector.RemoteObject.prototype.): (WebInspector.RemoteObject.prototype.setPropertyValue): These files are mechanical removals of code that used or implemented the interfaces I removed. Source/WebInspectorUI: * UserInterface/InspectorBackendCommands.js: Updated by script. LayoutTests: * inspector/debugger/debugger-change-variable-expected.txt: Removed. * inspector/debugger/debugger-change-variable.html: Removed. This test was failing because we don't support this API. * platform/mac/inspector/console/command-line-api-expected.txt: This test changed line numbers because I changed inspector .js files. git-svn-id: http://svn.webkit.org/repository/webkit/trunk@155589 268f45cc-cd09-0410-ab3c-d52691b4dbfc
1f96f80f