poli0981andClaude Opus 5 36c39f3185 fix(edit): localized failures, and a search that collapses again
**#edit and #export showed a raw English Chrome string as the entire message.**
docs/02 §7 requires a localized sentence plus a separate technical block, and
LegalGate carries a comment describing this exact mistake as a defect that was
already fixed once — writing `detail ?? t(key)` looks like a sensible fallback,
but the raw string is almost always present, so the translation becomes dead
code. Three sites still had it: EditTab's load failure, ExportTab's load
failure, and ExportTab's export toast. A Vietnamese or Japanese user got an
untranslated Chrome message as their whole explanation.

One ErrorCallout now owns that contract, so there is a single place it can be
got wrong, and all three tabs go through the shared describeError.

**Clearing the search box rendered the whole tree in one synchronous pass.**
Search-opened ancestors merge into `expanded` (deliberately — a render-time
union made the disclosure button and ArrowLeft dead keys), but nothing ever
un-merged them. A one-character query expands most of a large profile, and
clearing the box then rendered every row the search had opened at once, with no
virtualization behind it; the 150 ms debounce delayed that growth without
bounding it. src/lib/edit/search-expansion.ts tracks search-owned ids
separately, and toggling a folder transfers it to the user so the collapse
cannot steal it back.

**"Keep the first of each" targeted nodes it cannot delete, then gave up
silently.** The duplicate list had no isEditable filter — unlike the
single-delete path — so duplicates inside a policy-managed subtree were offered
for bulk deletion, and the browser rejects every one of them. The loop then
abandoned the rest on the first rejection, leaving a partial delete measured
against a dialog that had promised an exact number, with no way to tell how many
copies remained. deleteEach never throws and reports how far it got.

EditTab was at 481/500 before this, so the ARIA tree container came out into
TreeList.svelte first — 466 now, and the tree pattern lives somewhere it is not
surrounded by loading, searching, mutation and five dialogs. That extraction
immediately caught a real bug the shorthand had hidden: `{ontoggle}` bound
`window.ontoggle`, not the local `toggle`.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-03 19:00:27 +07:00
2026-07-25 19:21:07 +07:00

BookmarkMagic

License: GPL-3.0-or-later CI CodeQL Runtime dependencies: 0

Move your bookmarks between browsers the simple way: with a file. No account, no cloud sync, 100% offline.

A Chrome (MV3) extension for importing, exporting and editing bookmarks and folder trees. English · Tiếng Việt · 日本語.

Screenshots

Edit Export
The edit tree, showing bookmarks with their domains The export tab: folder picker on the left, format cards on the right
Settings About
Settings: language, theme, and four defaults About: version, links, third-party statement, donate links and the legal block

What it does

  • Import HTML, JSON or CSV bookmark files, with a full preview first — counts, folders, depth, duplicates and warnings before anything is written.
  • Choose how: into a new dated folder (the safe default), merged into your existing folders, or replacing everything. Replace saves a JSON safety backup first and deletes nothing until that backup is proven.
  • Export everything, or just the folders you pick, to HTML (Chrome, Edge, Brave, Firefox, Safari, Vivaldi, Opera), JSON, CSV or Markdown.
  • Edit the tree: search, rename, drag & drop, create folders, delete, and find duplicate links — every action reachable from the keyboard.

Privacy

This is the whole point of the project, so it is worth being precise.

  • No network access at all. Not analytics, not telemetry, not update pings. There is no server. A grep gate (npm run guard) fails the build if anyone adds fetch, XMLHttpRequest, WebSocket, EventSource or sendBeacon.
  • Exactly two permissions: bookmarks and storage. No host permissions, no content scripts, no background worker. Two gates enforce it: a unit test over wxt.config.ts, and npm run check:manifest, which CI runs against the built manifest.json — because a build can add what the config never asked for.
  • Zero runtime dependencies. Nothing third-party ships in the extension.
  • Settings use chrome.storage.local, never storage.sync, so even your preferences stay off any vendor cloud.

Full policy: legal/PRIVACY.md.

Honest limitations

  • Favicons cannot be imported — the bookmarks API has no favicon field.
  • Imported bookmarks get today's date. Chrome does not let an extension set a bookmark's original creation date. Your exported files keep the real ones.
  • CSV is a flattened view: empty folders and "which folder is the toolbar" are not preserved. Use HTML or JSON for a faithful backup.
  • Markdown is share-only — BookmarkMagic cannot read it back.

Install

From the Chrome Web Store: here

From source:

npm ci && npm run build

Then load .output/chrome-mv3/ at chrome://extensions with Developer mode on.

Development

npm run dev

npm run verify is the gate everything else answers to — lint, type-check, knip, the grep gate and the test suite, in that order. It must be green before every commit.

The docs/ directory is the binding specification, not notes: where code and docs disagree, the docs win. Start with CLAUDE.md, then docs/00–docs/02.

Contributing

Bug reports and translation fixes are welcome — the issue forms ask for what is needed, and none of them requires you to write code.

If a bookmark file will not import, that is the most useful report there is, because the sample becomes a permanent test. Sanitize it first:

node scripts/sanitize-bookmarks.mjs your-bookmarks.html

That strips every address and title but keeps the structure, encoding and timestamps a parser bug depends on — so the sanitized file still reproduces the problem without handing over your browsing history.

CONTRIBUTING.md has the rest: the setup, the rules that are not negotiable, and how a reported file becomes a regression test.

Security issues: please follow SECURITY.md rather than opening a public issue.

Support development

Entirely optional — BookmarkMagic is free software either way.

GitHub Sponsors · Ko-fi · Buy Me a Coffee · Patreon · PayPal

Licence

GPL-3.0-or-later. Also see legal/EULA.md, legal/DISCLAIMER.md and legal/THIRD_PARTY_NOTICES.md.

Not affiliated with or endorsed by Google, Chrome, or any browser vendor. Browser names are trademarks of their respective owners.

S
Description
No description provided
Readme GPL-3.0
3 MiB
0 Stars 1 Watchers 0 Forks
Languages
TypeScript 75.8%
Svelte 14.5%
JavaScript 9.2%
CSS 0.4%