LotusGuild/cinny
3
0
Fork 0
Code Issues 27 Pull Requests 5 Actions Packages Projects Releases Wiki Activity

"On-device translation isn't available… use … the Lotus desktop app": the Linux and macOS desktop apps (WebKit) can't translate either, and they show this advice to people already in the app #349

New Issue
Closed
opened 2026-10-11 01:13:09 -04:00 by jared · 0 comments
jared commented 2026-10-11 01:13:09 -04:00
Owner
Copy Link
Copy Source

Message translation uses only Chromium's on-device Translator / LanguageDetector APIs (utils/translation/engine.ts; deliberately no network engine ✔). Where they're missing, Settings → General shows (General.tsx:2763):

On-device translation isn't available in this browser. Use a Chromium desktop browser (Chrome/Edge 138+) or the Lotus desktop app.

Checked:

  • Chromium (Playwright build): Translator ✔ and LanguageDetector ✔, and the settings work;
  • Firefox: both missing, and this message shows;
  • WebKit 26.6 (Playwright's build, the engine behind the Linux app's WebKitGTK and the macOS app's WKWebView): Translator: false, LanguageDetector: false.

So on Linux and macOS the desktop app can't translate either. It shows this same message inside the desktop app, sending people to the app they're already using. Windows (WebView2, Chromium-based) wasn't checked here.

Fix:

  • Word it by platform: in the desktop app say "isn't available in this version of the desktop app" (with Windows-only support if WebView2 has the API), and on the web, recommend only Chrome/Edge 138+.
  • isTauri() / the user agent tell the cases apart.
  • Optionally hide the per-message Translate action entirely when isSupported() is false, rather than offering a dead end.

Found in the October 2026 client audit (Playwright against a local Synapse + LiveKit stack, plus code reading). Code refs are at cinny 30e2dbcd, cinny-desktop 8f67ec7, element-call 3b0050e8.

Message translation uses only Chromium's on-device `Translator` / `LanguageDetector` APIs (`utils/translation/engine.ts`; deliberately no network engine ✔). Where they're missing, Settings → General shows (General.tsx:2763): > On-device translation isn't available in this browser. Use a Chromium desktop browser (Chrome/Edge 138+) **or the Lotus desktop app.** **Checked:** - Chromium (Playwright build): `Translator` ✔ and `LanguageDetector` ✔, and the settings work; - Firefox: both missing, and this message shows; - **WebKit 26.6** (Playwright's build, the engine behind the Linux app's WebKitGTK and the macOS app's WKWebView): `Translator: false, LanguageDetector: false`. So on **Linux and macOS** the desktop app can't translate either. It shows this same message *inside* the desktop app, sending people to the app they're already using. Windows (WebView2, Chromium-based) wasn't checked here. **Fix:** - Word it by platform: in the desktop app say "isn't available in this version of the desktop app" (with Windows-only support if WebView2 has the API), and on the web, recommend only Chrome/Edge 138+. - `isTauri()` / the user agent tell the cases apart. - Optionally hide the per-message **Translate** action entirely when `isSupported()` is false, rather than offering a dead end. --- _Found in the October 2026 client audit (Playwright against a local Synapse + LiveKit stack, plus code reading). Code refs are at cinny `30e2dbcd`, cinny-desktop `8f67ec7`, element-call `3b0050e8`._
jared added the priority: lowuxarea: settings labels 2026-10-11 01:13:09 -04:00
jared closed this issue 2026-10-19 00:47:27 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
a11y
Accessibility: keyboard, screen reader, contrast, motion
 area: appearance
Client area: appearance
 area: auth-session
Client area: auth-session
 area: build-ci
Client area: build-ci
 area: calls
Client area: calls
 area: desktop
Client area: desktop
 area: media
Client area: media
 area: messaging
Client area: messaging
 area: mobile
Client area: mobile
 area: moderation
Client area: moderation
 area: navigation
Client area: navigation
 area: notifications
Client area: notifications
 area: settings
Client area: settings
 area: threads
Client area: threads
 bug
Something is not working
 dependencies
Third-party package versions and advisories
 docs
README / LOTUS_* docs wrong or missing
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 needs-human-review
performance
Re-render storms, leaks, heavy work on hot paths
 planning
priority: critical
Data loss, security hole, or crash on a main path
 priority: high
Broken feature or serious usability problem
 priority: low
Minor issue or polish
 priority: medium
Wrong behaviour in an edge case or notable degradation
 qa
Manual QA: shipped, needs a human in a real environment
 question
More information is needed
 research
security
XSS, unsafe URLs, data leaks, auth/session
 tech-debt
Code health, dead code, fragile patterns
 ux
Usability or visual inconsistency
 wontfix
This won't be fixed
No labels area: settings priority: low ux
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
cole (Cole Keller) jared (Jared Vititoe) nathan (Nathan Vititoe)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: LotusGuild/cinny#349