Thank you.
That helps more than you’d think — it goes straight into what we fix next.
Two of the ways that happens are things we can point at, and neither of them reports an error — which is why “it just does nothing” is the only symptom you get.
Chrome keeps a set of combinations for itself and consumes them before any page or extension
sees the key: Ctrl+T, Ctrl+W, Ctrl+N,
Ctrl+Shift+T and others. The extension will happily let you record
one of those, and it will then never fire, because the press never arrives. Chrome also refuses to
run any extension on its own internal chrome:// pages and on the Web Store.
A third one used to be ours, and is not any more: site rules written as
GitHub.com, https://github.com or github.com/user once matched
nothing and said nothing about it. Since version 1.0.2 those are read as github.com when
you save the rule in the options page, and the one form that cannot be guessed at — a wildcard
with no dot, such as *github.com — is named under the box instead of failing quietly.
A rule that came in through the settings import is the one case the options page has not looked at:
open it there and save it once.
The FAQ shows what the options page does with each form.
Nothing about you was sent. Only the reason you picked was counted.