Where Chromium's on-device Translator / LanguageDetector APIs are missing, Settings → General said: "Use a Chromium desktop browser (Chrome/Edge 138+) or the Lotus desktop app." The Linux and macOS desktop apps (WebKitGTK / WKWebView) lack those APIs too, so they showed this advice to people already in the app.
Change: new translationUnavailableText(desktopApp), picked with isTauri():
Desktop app: "On-device translation isn't available in this version of the desktop app. It works in Chrome or Edge 138+ on a computer."
Web: "On-device translation isn't available in this browser. Use Chrome or Edge 138+ on a computer."
The per-message Translate action was already hidden where the engine is unsupported (Message.tsx), so there's no dead end there. Windows (WebView2) isn't special-cased: where it has the APIs, this text never shows.
Unit test for both texts. No browser run, since this is a text change. tsc clean · ESLint clean.
Fixes #349.
Where Chromium's on-device Translator / LanguageDetector APIs are missing, Settings → General said: "Use a Chromium desktop browser (Chrome/Edge 138+) **or the Lotus desktop app.**" The Linux and macOS desktop apps (WebKitGTK / WKWebView) lack those APIs too, so they showed this advice to people already in the app.
**Change:** new `translationUnavailableText(desktopApp)`, picked with `isTauri()`:
- **Desktop app:** "On-device translation isn't available in this version of the desktop app. It works in Chrome or Edge 138+ on a computer."
- **Web:** "On-device translation isn't available in this browser. Use Chrome or Edge 138+ on a computer."
The per-message **Translate** action was already hidden where the engine is unsupported (`Message.tsx`), so there's no dead end there. Windows (WebView2) isn't special-cased: where it has the APIs, this text never shows.
Unit test for both texts. No browser run, since this is a text change. `tsc` clean · ESLint clean.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
Where the on-device Translator/LanguageDetector APIs are missing,
Settings said to use Chrome/Edge "or the Lotus desktop app", but the
Linux and macOS apps (WebKit) lack them too, and showed the advice to
people already in the app. Word it by platform. (The per-message
Translate action was already hidden where unsupported.)
Fixes#349
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #349.
Where Chromium's on-device Translator / LanguageDetector APIs are missing, Settings → General said: "Use a Chromium desktop browser (Chrome/Edge 138+) or the Lotus desktop app." The Linux and macOS desktop apps (WebKitGTK / WKWebView) lack those APIs too, so they showed this advice to people already in the app.
Change: new
translationUnavailableText(desktopApp), picked withisTauri():The per-message Translate action was already hidden where the engine is unsupported (
Message.tsx), so there's no dead end there. Windows (WebView2) isn't special-cased: where it has the APIs, this text never shows.Unit test for both texts. No browser run, since this is a text change.
tscclean · ESLint clean.🤖 Generated with Claude Code
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5