Skip to content

Web Translation API #339

Open
Open

Description

@domenic

WebKittens

No response

Title of the spec

Web Translation API

URL to the spec

No spec yet; please see the explainer

URL to the spec's repository

https://github.com/WICG/translation-api

Issue Tracker URL

No response

Explainer URL

No response

TAG Design Review URL

w3ctag/design-reviews#948

Mozilla standards-positions issue URL

mozilla/standards-positions#1015

WebKit Bugzilla URL

No response

Radar URL

No response

Description

This is an early-stage idea. However, we'd love early engagement from other implementers to make sure what we're designing fits well with their architecture.

The TAG design review and the issue tracker has some summaries of our current open questions.

Activity

  1. annevk commented on Apr 29, 2024

    @annevk
    Contributor

    This seems pretty interesting.

    It's not clear that the "download a language pack" approach can work. That results in XSLeaks attacks we've been trying to rid the web platform of.

    It's also not clear that a server-side approach is a good fit. At that point it's essentially a fetch() wrapper.

  2. added
    from: GoogleProposed, edited, or co-edited by Google.
    venue: WICGProposal is incubated in the Web Incubator Community Group
    on May 1, 2024
  3. domenic commented on May 7, 2024

    @domenic
    Author

    It's not clear that the "download a language pack" approach can work. That results in XSLeaks attacks we've been trying to rid the web platform of.

    Please join the discussion on webmachinelearning/translation-api#3!

  4. sandstrom commented on Sep 24, 2025

    @sandstrom

    Any updates from the Safari team on this?

    It seems like the concern mentioned above about XSLeaks attacks have been elaborated on here:

    https://webmachinelearning.github.io/writing-assistance-apis/#privacy

  5. renchap commented on Jan 22, 2026

    @renchap

    Chiming in with my Mastodon hat: we have a core feature of allowing users to translate Mastodon posts into their own language, which currently relies on backend API calls (that are forwarded to various translation services that can be configured by the server admin). This creates significant costs for server admins and we would love to be able to replace it with a local translation feature provided by the browser.

    We have an open Pull Request to implement the proposed API into Mastodon, but we are waiting to have at least 2 browser engines support the proposal before using it.

  6. tomayac commented on Jan 22, 2026

    @tomayac

    We have an open Pull Request to implement the proposed API into Mastodon, but we are waiting to have at least 2 browser engines support the proposal before using it.

    The PRs in question: mastodon/mastodon#35369 (translation) and mastodon/mastodon#35345 (language detection).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

from: GoogleProposed, edited, or co-edited by Google.venue: WICGProposal is incubated in the Web Incubator Community Group

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions