1544118 - Move nsINode::localize to use DocumentL10n::TranslateFragment

Status: RESOLVED FIXED

(Core :: Internationalization, task, P2)

Description

[Zibi Braniecki [:zbraniecki][:gandalf]]

Once we land bug 1503657, we can refactor deeper integration of Fluent into DOM to stop having to go back and forth between C++ and JS when localizing fragments.

The only call from C++ to JS is the call for strings which is FormatMessages. Everything else can stay within C++.

Comment 1

[Zibi Braniecki [:zbraniecki][:gandalf]]

Initial talos looks promising: https://treeherder.mozilla.org/perf.html#/compare?originalProject=try&originalRevision=843ce8172bef5f383fc321e02fd8949bcb9f0272&newProject=try&newRevision=9493b9da9b7153e456fee1ed6cc365c24479dd21

Comment 2

[Zibi Braniecki [:zbraniecki][:gandalf]]

Attachment: Bug 1544118 - Move nsINode::localize to use DocumentL10n::TranslateFragment.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/bc48855c4da8
Move nsINode::localize to use DocumentL10n::TranslateFragment. r=smaug

Comment 4

[Raul Gurzau (:RaulG)]

https://hg.mozilla.org/mozilla-central/rev/bc48855c4da8