Add native translation support based on the Translator API #9070
+209
−45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds native translation support based on the Translator API that shipped in Chrome 138 as a progressive enhancement. On non-supporting browsers, the current behavior of linking to Google Translate is maintained.
The original post from the examples below was written in English and translated to German.
Translating a post with the Translate button
This shows the translation in lieu of the original text, with the option to toggle back to the original.
Translating a post with the Translate post menu item:
This opens a modal dialog with the translation.
Translating a direct message with the Translate message menu item:
Since this all happens on the client-side, this is a huge privacy win, and compatible with end-to-end encrypted DMs.