Changelog
A date here is the day we packaged that version, which is the only date we can show you a source for. Chrome reviews every version before it reaches anyone, and the store does not tell us when a given version arrived in your browser — so the day you got it is later, by an amount we cannot see. A version can also be superseded by the next one before its review finishes, which is why two of these share a date. The badge below marks the version that is on the store right now.
1.2.2 — packaged 11 September 2026
Two ways a tab could end up with shortcuts that quietly did nothing, both fixed. If the extension failed to read your settings the first time a page loaded — which happens when the browser is restoring many tabs at once, or right after the extension updates — that tab stayed dead until you reloaded it, with no error anywhere. It now retries, and your next keypress is itself a retry.
The second one hit at the worst moment: right after you grant permissions. Tabs that were already open got no shortcuts at all, because the browser only applies a new registration to pages loaded afterwards. Those tabs are now covered without reloading anything.
1.2.1 — packaged 8 September 2026
The pointer to our other extension, in the popup and on the options page, now says what is actually true — Highlight Reader is on the store and free — instead of describing it as something coming later. Carried through all 24 locale files in the same release.
1.2.0 — packaged 5 September 2026
A three-step tour on first install, the permissions asked once up front instead of one prompt per action, and a visible confirmation the first time a shortcut fires. Removing the extension now opens a short page that asks why, because the store only tells us that someone left, never what went wrong.
Two real bugs fixed: shortcuts that did not fire inside an iframe, and a held-down key that repeated its action instead of running it once.
1.1.0 — packaged 5 September 2026
The options page opens itself on first install, so a fresh install lands somewhere you can actually do something. One rating prompt, once, after seven days and twenty uses — and never again whether you answer it or not.
1.0.1 — packaged 31 August 2026
Ready-made templates so a new install can have a working set in one click. Browser-level shortcuts that Chrome dispatches itself, so they keep working on pages where an extension cannot see keystrokes. Three data-loss bugs fixed: a settings write that failed silently, an import merge that dropped rules sharing a key with different site scopes, and an import that reused source ids and collided.
The interface was translated into 21 languages in this release, including Arabic, Hebrew and Persian — right-to-left layouts included, with key combinations kept left-to-right because a physical keyboard does not mirror. It is 24 languages today.
1.0.0 — packaged 27 August 2026
Went up on the Chrome Web Store 31 August 2026.
First release. Twenty-nine built-in actions, per-shortcut site rules with an allow or deny list, export and import as a JSON file with an undo snapshot, and settings that sync through your own Chrome profile.
Requires Chrome 116 or later. Installs with no access to any website.
How releases work here
Every version is smoke-tested before it is packaged, and the package is verified file by file against the source it was built from, so what reaches the store is what we wrote. Our intent is that a fix ships as its own release rather than waiting to be bundled into a rewrite — that is what broke the extension we set out to replace.