RESOLVED FIXED 67711
Web Inspector: [REGRESSION] Clear console shortcut Ctrl + L broken
https://bugs.webkit.org/show_bug.cgi?id=67711
Summary Web Inspector: [REGRESSION] Clear console shortcut Ctrl + L broken
Alexander Pavlov (apavlov)
Reported 2011-09-07 08:44:41 PDT
This was regressed in r93769. Patch to follow
Attachments
[PATCH] Suggested fix (2.57 KB, patch)
2011-09-07 09:10 PDT, Alexander Pavlov (apavlov)
yurys: review-
[PATCH] Comments addressed (3.15 KB, patch)
2011-09-08 02:10 PDT, Alexander Pavlov (apavlov)
yurys: review+
Alexander Pavlov (apavlov)
Comment 1 2011-09-07 09:08:56 PDT
Alexander Pavlov (apavlov)
Comment 2 2011-09-07 09:10:00 PDT
Created attachment 106590 [details] [PATCH] Suggested fix
Yury Semikhatsky
Comment 3 2011-09-07 23:44:27 PDT
Comment on attachment 106590 [details] [PATCH] Suggested fix View in context: https://bugs.webkit.org/attachment.cgi?id=106590&action=review > Source/WebCore/inspector/front-end/ConsoleView.js:495 > this._shortcuts[shortcutK.key].isMacOnly = true; I'd suggest you get rid of the isMacOnly flag and set this handler only if current platform is Mac, this way you'll be able to share the handler.
Alexander Pavlov (apavlov)
Comment 4 2011-09-07 23:59:21 PDT
(In reply to comment #3) > (From update of attachment 106590 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=106590&action=review > > > Source/WebCore/inspector/front-end/ConsoleView.js:495 > > this._shortcuts[shortcutK.key].isMacOnly = true; > > I'd suggest you get rid of the isMacOnly flag and set this handler only if current platform is Mac, this way you'll be able to share the handler. Does it make sense to have the isMacOnly flag at all? Can't believe it's the only instance of its usage...
Alexander Pavlov (apavlov)
Comment 5 2011-09-08 02:10:51 PDT
Created attachment 106712 [details] [PATCH] Comments addressed
Alexander Pavlov (apavlov)
Comment 6 2011-09-08 06:57:42 PDT
Pavel Feldman
Comment 7 2011-09-27 09:39:50 PDT
*** Bug 68907 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.