| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| read-frogextension-1.46.4-chrome.zip | 2026-08-21 | 6.6 MB | |
| read-frogextension-1.46.4-edge.zip | 2026-08-21 | 6.6 MB | |
| read-frogextension-1.46.4-firefox.zip | 2026-08-21 | 6.6 MB | |
| read-frogextension-1.46.4-sources.zip | 2026-08-21 | 2.6 MB | |
| README.md | 2026-08-21 | 2.1 kB | |
| v1.46.4 source code.tar.gz | 2026-08-21 | 25.9 MB | |
| v1.46.4 source code.zip | 2026-08-21 | 26.8 MB | |
| Totals: 7 Items | 75.1 MB | 0 | |
Patch Changes
-
#2106
df8f243Thanks @taiiiyang! - feat(subtitles): use the subtitles-AI icon and explain AI transcription in a tooltip -
#2107
b022effThanks @mengxi-ream! - fix(translation): tell users to reload the page when the extension was updated, instead of showing the raw "Extension context invalidated." error -
#2109
59e155eThanks @ananaBMaster! - fix(translate): stop the giant-paragraph split from stranding a container's own text
Tall containers are split into their descendant paragraphs so viewport-lazy translation still applies (#1881). That split silently drops any text the container holds directly, which is harmless on a nested <article> but catastrophic on <br>-delimited article bodies, where the bare text is the article — a Blogger post kept 8% of its text and paulgraham.com/greatwork.html kept 1.1%, while the incidental inline <i> got its own translation inserted mid-sentence.
- Refuse the split when the container owns prose of its own and has a block-level child, so the translate path re-segments it into per-line runs instead
- Keep splitting when the container owns no prose (unchanged for docs.docker.com), when its own text carries no letters (separators, dates), when it has no block child to re-segment on, when it is
<body>, or when the split already yields more units than the gating cap - Apply the same guard on the translate side's giant fallback, so both paths make one decision