Skip to content

Release v0.1.3: offer a reload when a tab has no content script - #4

Merged
backnotprop merged 2 commits into
mainfrom
release/0.1.3
Nov 1, 2026
Merged

backnotprop merged 2 commits into
mainfrom
release/0.1.3

Conversation

@backnotprop

Copy link
Copy Markdown
Contributor

Refs #2

Tabs opened before App Notes was installed, or left open while it updates, have no content script until they reload. The popup called these pages unavailable and disabled Enable annotations, with no hint that a reload would fix it.

The popup now shows Reload page in that state. Two cases never offer it:

  • Browser store pages, where extensions can't run.
  • A page that is still silent after one reload, so nobody gets stuck in a reload loop.

No new permissions. This also bumps the version to 0.1.3, because 0.1.2 is already live and the store needs a higher version. 0.1.3 ships this change and #3.

Testing

  • bun run release:verify passes, with 68 tests.
  • Chromium checks of the built extension pass: a tab opened before install through to annotating, a tab open while the extension is replaced, the real Chrome Web Store, chrome:// pages, the reload-loop guard, and a normal tab.

Tabs opened before install, or left open across an update, have no content
script until they reload. The popup called these pages unavailable and
disabled its controls, which looks like a broken extension. Offer a reload
instead, except on browser store pages or after a reload did not help.
@backnotprop
backnotprop merged commit 49b452e into main Nov 1, 2026
1 check passed
@backnotprop
backnotprop deleted the release/0.1.3 branch November 1, 2026 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant