FAQ
Overview · Actions · Site rules · Export & import · Permissions · FAQ
My shortcut does nothing while I am typing. Is it broken?
No — that is deliberate. Text fields, text areas, select elements and anything
contenteditable are left alone, including inputs inside a shadow DOM.
Hijacking keys while someone is writing is the single most common complaint about
shortcut extensions. There is a setting to turn the protection off if you want it.
Which version am I on, and what changed in it?
The version is on the extension's options page, and on Chrome's own
chrome://extensions page. What went into each release is listed in the
changelog.
Does it interfere with Chinese, Japanese or Korean input?
No. While an input method is composing, key events are ignored entirely — the extension checks for composition before it looks at anything else.
I use a non-QWERTY layout. Will my shortcuts still work?
Yes. Letters and digits are captured by physical key position rather than by the character produced, so a shortcut recorded on one layout keeps working on another.
I bound Ctrl+T (or Ctrl+W) and nothing happens
Chrome handles a set of combinations itself, before any page or extension sees them — Ctrl+T, Ctrl+W, Ctrl+N, Ctrl+Shift+T and others, plus the function-key row on some systems. No extension can intercept those, because the key press never reaches the page.
This is a browser rule, not a limitation we can lift. The extension will let you record such a combination and it will simply never fire. Pick a combination Chrome does not already own — Alt-based ones are the safest, which is why the defaults use them.
My site rule does not match and I cannot see why
Patterns are compared against the page's hostname, in lower case, with nothing else attached. What you type is put into that shape when the rule is saved:
| Written as | Saved as |
|---|---|
GitHub.com | github.com — hostnames are lower case. |
https://github.com | github.com — the scheme is not part of a hostname. |
github.com/user | github.com — paths are not part of a hostname, so the rule covers the whole site. |
*github.com | Left exactly as written, and named under the box: a wildcard needs a dot. Both *.github.com and plain github.com would cover the subdomains, so the extension does not pick one for you. |
Write the bare hostname. Capitals, a https:// prefix, a path or a port
are removed when you save the rule in the options page, so GitHub.com and
https://github.com/user both end up as github.com. A line the
options page cannot read — a wildcard with no dot, such as
*github.com — is named underneath the box instead of failing
quietly.
If a rule that arrived in an imported settings file does not match, open that rule in the options page and save it once: that is the step which puts what is written into the shape above.
Can I use a single key with no modifier?
Yes, and the options page will warn you when you do. A bare key is fine for something like J to move to the next tab, but it will collide with typing on any site where you can type — which is why the typing protection above matters.
Do my shortcuts sync between computers?
They sync through your own Chrome profile, the same way your bookmarks do. We have no server, so nothing passes through us. If you are not signed into Chrome, use export and import.
Why do shortcuts not work on some pages?
Chrome does not allow extensions to run on its own internal pages —
chrome:// addresses, the Chrome Web Store, and in some configurations the
new tab page. That is a browser rule and no extension can change it.
Can two shortcuts use the same keys?
Yes, if their site scopes do not overlap. The first matching rule wins, so put the narrower one first. Two identical rules with overlapping scope means the second never fires.
What happens to my shortcuts if I uninstall?
Chrome removes the extension's storage. If you want to keep your shortcuts, export them first — the file is yours and does not expire.
Is there a paid version?
No. Version 1.2.3, the one on the store today, is entirely free with no paid tier, no account, and no feature held back. If that ever changes we will say so plainly rather than removing something you already use.
Something here is wrong, or my question is not answered
Email support@rehobothbuilds.com. A person reads it. See Support for what to include.