Skip to content

v1.3.0 — table-cell translations, first-run guidance

Choose a tag to compare

@belliedmonkey belliedmonkey released this 01 Aug 03:20
· 111 commits to main since this release
ab31eb0

What's changed

Fixed — a table cell now takes its translation as a child, not a sibling. (#59 / #60)

An element placed next to a display: table-cell unit lands inside the <tr>, where the
browser wraps it in an anonymous table cell — so the translations became a whole extra
column and the table's intrinsic width roughly doubled. On a floated Wikipedia infobox the
prose column beside it collapsed to ~115px, two or three words per line, while paragraphs
below the table were untouched.

The fix is generic: no hostname or selector entered the segmenter or the renderer. Wikipedia
is the motivating case and the verified site, not a special case in the code — and it now has
a regression fixture of its own (fixture 30, red before the fix).

New — first-run guidance. (#62 / #63)

There was no onboarding at all, and the default engine needs no key and works immediately —
which is exactly the trap, because that endpoint is not stable: it can hand back your
original text unchanged. So the default path was install → translate → sometimes get your own
text back → conclude the extension is broken.

Now the popup and the settings page carry a note that says where you stand before a bad
first result: an engine that needs an API key says so, and the free no-key engine is described
for what it is — fine for a first look, not a stable endpoint. A configured engine shows
nothing. First run marks the toolbar icon with a dot, cleared when the popup first opens.

The free engine is not removed or hidden. Zero-config trial is a real feature; what was
wrong is that users landed on it silently.

Repo — CI (unit tests on Node 16 + 22, all three build flavors), issue templates including
a site adaptation request form, and a rewritten README (English + 简体中文, store-first).

Tests: 87 unit tests, 30 layout fixtures, all green.

Install

Most people should install from a store rather than from source:

  • iPhone / iPad / Mac — SafariApp Store
  • Chrome / EdgeChrome Web Store
  • Firefox → still in review on addons.mozilla.org. Until it clears, the .xpi below is the
    way in: about:debugging → This Firefox → Load Temporary Add-on.
Asset For
belliedmonkeytranslator.zip Chrome / Edge — unzip, then chrome://extensions → Developer mode → Load unpacked
belliedmonkeytranslator-firefox.xpi Firefox — about:debugging → Load Temporary Add-on

⚠️ This tag is not a statement about what is live

v1.3.0 marks the source that was submitted to the stores — not a version that has shipped
everywhere. Review is per-platform and each store rolls out on its own schedule. At the moment
this tag was cut, the live versions were iOS 1.2.0, macOS 1.2.0 and Chrome Web Store 1.2.0,
with Firefox 1.2.0 still queued at AMO. The store pages above are the only reliable answer to
"what can I install right now".