RESOLVED FIXED 60811
Web Inspector: [REGRESSION] Completion while on a breakpoint is not working.
https://bugs.webkit.org/show_bug.cgi?id=60811
Summary Web Inspector: [REGRESSION] Completion while on a breakpoint is not working.
Pavel Feldman
Reported 2011-05-13 15:16:39 PDT
I thought we had a test for this one. Surprised it does not work.
Attachments
Patch (8.70 KB, patch)
2011-05-18 07:24 PDT, Pavel Feldman
no flags
Patch (9.97 KB, patch)
2011-05-18 08:28 PDT, Pavel Feldman
no flags
Patch (10.00 KB, patch)
2011-05-18 08:33 PDT, Pavel Feldman
no flags
Pavel Feldman
Comment 1 2011-05-18 07:24:09 PDT
Alexander Pavlov (apavlov)
Comment 2 2011-05-18 07:28:14 PDT
Comment on attachment 93910 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=93910&action=review > Source/WebCore/inspector/front-end/ScriptsPanel.js:378 > + selectedCallFrameVariables: function() Any reason for this not being a getter?
Yury Semikhatsky
Comment 3 2011-05-18 07:45:01 PDT
Comment on attachment 93910 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=93910&action=review > LayoutTests/inspector/debugger/debugger-completions-on-call-frame.html:30 > + InspectorTest.addResult(golden[i]); Would be better to addResult("FAIL") in case of missing property. > Source/WebCore/inspector/InjectedScriptSource.js:484 > + for (var name in scopeChain[i]) This will be too slow for global scope. > Source/WebCore/inspector/InjectedScriptSource.js:497 > + for (var name in scopeVariableNames) I'd rather resurrect the command that allowed to quickly request all completions.
Pavel Feldman
Comment 4 2011-05-18 08:28:18 PDT
Pavel Feldman
Comment 5 2011-05-18 08:33:54 PDT
Pavel Feldman
Comment 6 2011-05-18 08:53:09 PDT
Comment on attachment 93920 [details] Patch Clearing flags on attachment: 93920 Committed r86768: <http://trac.webkit.org/changeset/86768>
Pavel Feldman
Comment 7 2011-05-18 08:53:18 PDT
All reviewed patches have been landed. Closing bug.
Alexey Proskuryakov
Comment 8 2011-05-19 11:53:18 PDT
Note You need to log in before you can comment on or make changes to this bug.