Pressing 'Delete' key in bookmark manager's search box deletes bookmark.

chrome/browser/resources/bookmark_manager/js/main.js

Index: chrome/browser/resources/bookmark_manager/js/main.js
diff --git a/chrome/browser/resources/bookmark_manager/js/main.js b/chrome/browser/resources/bookmark_manager/js/main.js
index acfc3d7db701566ae61ea65a88c2c33d5ebf04f4..e1b6b8bd9a4fe4050a6e9acc2e0589df350c1610 100644
--- a/chrome/browser/resources/bookmark_manager/js/main.js
+++ b/chrome/browser/resources/bookmark_manager/js/main.js
@@ -496,6 +496,11 @@ function handleCanExecuteForDocument(e) {
       e.canExecute = e.currentTarget.activeElement !== $('term');
       break;
 
+    case 'delete-command':
+      // If the search box is active, pass the delete command
+      e.canExecute = e.currentTarget.activeElement !== $('term');

[Bernhard Bauer, 2015/04/15 12:51:16]

Right. This means however that we will always make a decision whether the delete
command can execute. If the search field is not active, we want to delegate that
decision to canExecuteForList() and canExecuteForTree() below, so you want to
set canExecute (and break) only if the search field is active.

(BTW, this is why I suggested moving this code to a separate handler on the
search field: it removes the necessity of the activeElement check, and it avoids
conflating different reasons for allowing a command to execute or not, which is
what happens for the 'undo-command' case above.)

+      break;
+
     default:
       canExecuteForList(e);
       if (!e.defaultPrevented)