ScrKeyboard

ScrKeyboard is an on-screen keyboard built for operators of business web applications on touch screens: warehouse terminals, production floors, reception desks, CRM and order-entry systems. It is not a general-purpose accessibility keyboard — it is purpose-built for touch-screen workstations where a physical keyboard is awkward or missing, and where every extra panel takes space away from the operator's actual work. Features: - Three keyboard modes: letters, symbols (reached from the ?# key) for full punctuation, and a one-shot Polish diacritics mode (ĄĘ) that composes with Shift. - A punctuation column (full stop, comma, hyphen, at sign) on the numeric keypad, available in every mode, so dates, references and email addresses are always reachable. - A Tab key that moves focus to the next editable field without closing the keyboard, so a whole form can be completed without a physical keyboard. - One-tap quick phrases, global and per-site, with operator-chosen button colours and automatic black-or-white text for contrast. - CapsLock state remembered between sessions. - Enter or Ctrl+Enter confirmation mode, with the focused field automatically scrolled clear of the keyboard panel. - English and Polish interface. - Approved and blocked site rules with wildcard support, managed from a full options page; blocked rules always take precedence over approved ones. How it works: ScrKeyboard does nothing until you approve a site. Open the ScrKeyboard icon on the page you want to use it on and add the site — that is the whole setup. From then on, a keyboard panel docks to the bottom of the page whenever the operator focuses an editable field, and hides again on Enter, Close, or a click outside the field. Site access is requested as an optional Chrome permission at the moment you approve a site, never granted broadly at install, and you can review or revoke it at any time from Chrome's extension settings. Password fields are ignored unless a site's rule explicitly allows them. Privacy: ScrKeyboard has no backend and no analytics. It does not record or transmit anything typed into a page; it only relays keystrokes to the focused field, exactly as a physical keyboard would. The only things stored are your own configuration — site rules, phrases, language, colours — and the last CapsLock state, kept in Chrome's own extension storage and synced by Chrome itself if you are signed in. Nothing leaves the browser. ===== # Changelog All notable changes to this project will be documented in this file. The project follows semantic versioning during pre-production: - `0.0.x` for fixes. - `0.x.0` for new features. - `x.0.0` for production releases, with `1.0.0` as the first production version. ## 0.10.4 - 2026-08-18 ### Changed - Removed Vite's modulepreload polyfill from the build. The extension requires Chrome 116, which supports modulepreload natively, so the polyfill never ran — and it was the only fetch() call in the packaged extension, which made the Chrome Web Store's remote-code question harder to answer than it needed to be. ## 0.10.3 - 2026-08-18 ### Fixed - Fixed the options page review link pointing at a listing that does not exist. It now uses the published Chrome Web Store id, so it also works in an unpacked build, where the runtime id is generated locally. ## 0.10.2 - 2026-08-18 ### Fixed - Fixed the popup showing leftover development text ("Extension shell loaded. Setup controls will be added in the next milestone.") on every ordinary site instead of guidance for the operator. The popup now tells the operator to approve the current site, or confirms it is already approved, in both English and Polish. Also removed the unused, similarly stale `optionsStatus` message, which was never shown anywhere. - Re-encoded the extension icons as 8-bit RGBA, roughly halving their file size with no visual change. ## 0.10.1 - 2026-08-18 ### Fixed - Fixed the setup page showing "Enable ScrKeyboard" as the label for every approved-site rule, blocked-site rule and quick-phrase checkbox, making each row look as though it switched the whole extension on or off. Those per-row checkboxes now read "Enabled" ("Włączone" in Polish); the extension-wide switch in the setup section still reads "Enable ScrKeyboard". ## 0.10.0 - 2026-08-18 ### Added - Added a small credit footer to the options page, showing the extension version (read from the manifest at runtime), a link to leave a Chrome Web Store review, and project attribution links. ## 0.9.1 - 2026-08-17 ### Fixed - Fixed the numeric keypad's punctuation column (full stop, comma, hyphen, at sign) and the outermost main-keyboard keys being pushed off-screen and unreachable on windows roughly 861 to 963 pixels wide, by widening the point at which the keypad stacks below the main keyboard instead of sitting beside it. - Fixed Tab being able to move focus onto a password field on a site whose rule forbids password fields, when that field also carried `contenteditable="true"`. - Fixed the Polish diacritics mode staying armed after the keyboard panel is closed, so the next letter typed in a different field could silently come out as a diacritic instead of a plain letter. ## 0.9.0 - 2026-08-17 ### Added - Added a symbols mode with full punctuation, reachable from the `?#` key, including the forward slash and underscore needed for slashed dates and hyphenated references. - Added a punctuation column to the numeric keypad for full stop, comma, hyphen and at sign. - Added a Polish diacritics mode reachable from the `ĄĘ` key, combining with Shift and CapsLock. - Added a Tab key that moves focus to the next editable field without closing the keyboard. - Added extension icons in 16, 32, 48 and 128 pixel sizes, validated during the build. ### Changed - Changed `createKeyboardRows` to take a single layout state object instead of positional flags. ## 0.8.2 - 2026-08-17 ### Changed - Added a project state handover note fo…