{"issue":{"user":{"id":1240282,"login":"jsamuel","url":"https://api.github.com/users/jsamuel","avatar_url":"https://secure.gravatar.com/avatar/bc1d195cedb959a3946572b08ce9e7c7?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"bc1d195cedb959a3946572b08ce9e7c7"},"title":"add shortcut key to open the menu","milestone":null,"created_at":"2011-12-22T04:11:57Z","labels":[{"name":"extension","url":"https://api.github.com/repos/RequestPolicy/requestpolicy/labels/extension","color":"ededed"}],"state":"open","updated_at":"2011-12-22T04:11:59Z","id":2633133,"closed_at":null,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"html_url":"https://github.com/RequestPolicy/requestpolicy/issues/198","body":"If there were a shortcut/accelerator key to open the menu, RP could be reasonably used without a mouse. After the menu is open, arrow keys and enter are sufficient to interact with the whitelist.\r\n\r\nThere are two difficulties/areas of trickiness:\r\n 1. Choosing a correct shortcut key. We probably don't have to worry about localization other than making sure that the shortcut we pick isn't already used by default in some locales but not others (and is not used by popular extensions). As this probably won't relate directly to text, it probably won't need to differ between locales unless there are conflicts.\r\n 1. Knowing where to open the menu. That is, not only do we need to figure out which RP buttons are visible (toolbar, status/addons bar, both, none), we need to figure out what to do when the answer is \"none\" or \"both\".\r\n\r\nOne option to decrease the need to pick the perfect shortcut key would be to pick a good default but let it also be user-defined.\r\n\r\nRelated ticket: #47 added shortcut/accelerator keys to the redirect notification.","number":198,"url":"https://api.github.com/repos/RequestPolicy/requestpolicy/issues/198","comments":1,"assignee":null},"action":"opened"}