Skip to content

v0.1.13 — Typing no longer stutters over the in-browser model, and three fixes from Windows

Choose a tag to compare

@nyakojiru nyakojiru released this 07 Oct 22:03
· 56 commits to main since this release

Fixes from a full test on Windows: typing no longer stutters while the in-browser model checks, underlines stay under their words in a scrolling field, and saving settings no longer undoes a site switched on meanwhile.

Typing over the in-browser model

With the model running inside the browser, typing over a live check stuttered: in Brave on an RX 6600, 177 of 361 keystrokes took over 100 ms to paint while it generated, because the model and the page share the GPU. A live check now stops when typing resumes and runs again at the next pause. Actions you ask for are never stopped. After the fix: 0 of 339 and 0 of 340 slow keystrokes, with the checks still completing.

The 2.4 GB model download also ended for good on a single network error. It now tries three more times, and if that fails it says to click Download again. The files already fetched are kept.

Fixes

  • Underlines in a textarea with a scrollbar drifted away from their words after the first wrapped line. Seen in Brave on Windows, where the scrollbar is 16 px wide.
  • A settings page opened earlier, when saved, wrote back old lists: switching live checking on in a tab, then saving a provider change, switched it off again. Save now keeps what changed meanwhile, including words added to the dictionary.
  • When Chrome's built-in model download stops reporting progress (seen at 3% in Chrome 154 on Windows), the card now notices when the model becomes available. After 2 minutes without progress it says so and suggests restarting Chrome.

Also in this release

  • After ten applied suggestions over at least two days, ProofKey asks once for a rating. Only Chrome Web Store installs ask. The count stays in local storage and is never sent (PRIVACY.md).
  • A new store summary that leads with privacy: your text goes only to the AI you pick.
  • PRIVACY.md gains a threat model, and says plainly that settings, API keys included, use chrome.storage.sync.

How it is known

On the released tree, npm run verify reported 588 passing checks and no failures: unit checks, test:render and test:ext. Each fix above has a check that failed on the old code. The stutter, the scrollbar drift, the settings overwrite and the stalled download were found and re-tested in Brave and Chrome on Windows, on 2026-10-04 and 2026-10-05. Measurements are in MODELS.md and COMPATIBILITY.md.