During the translation phase, Chrome imports a JS <script> into the webpage and this script does all the translation work.
There's the language detection phase (another use case that I plan to ask on a separate e-mail) in which chrome does a .textContent and run the language detection off of it on that page's renderer thread. On Mon, Mar 3, 2014 at 4:31 PM, Jeff Muizelaar <jmuizel...@mozilla.com>wrote: > > On Mar 3, 2014, at 2:28 PM, Felipe G <fel...@gmail.com> wrote: > > > Hi everyone, I'm working on a feature to offer webpage translation in > > Firefox. Translation involves, quite unsurprisingly, a lot of DOM and > > strings manipulation. Since DOM access only happens in the main thread, > it > > brings the question of how to do it properly without causing hank. > > What does Chrome do? > > -Jeff > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
