The discussion addresses a bug where using Google Translate’s built-in browser feature causes a page to break with the error Failed to execute 'removeChild' on 'Node'. Don reports that the issue occurs after translating a page, causing the page to freeze, particularly during navigation. sam explains that the problem likely stems from Google Translate altering the DOM structure, which confuses Ember.js, the JavaScript framework used by Discourse. Don confirms this is not a Discourse issue but a conflict with Ember, referencing a similar past report in the Ember.js repository. sam notes that such DOM changes can disrupt Ember’s internal state management.
I changed Discourse language to e.g. French and translate it with built-in Google Translator to English.
Without Google Translate no error appears but when I turn on Google translator, after the first topic page change on New & Unread Topics the page will completely froze (broke).
I show it with topic page change but this issue also appears other pages…e.g. on /about when changing between /faq, /tos etc. with navigation if Google Translate enabled.
This is a tricky one, is this a Google bug or Discourse one? Built in translators fiddle with HTML structure that then makes Ember get super confused and lose its grounding.
Yes, unfortunately it seems that this is the case. You are right, this is not a Discourse issue but rather a conflict between Ember and Google Translate. I have also found a report from 5 years ago in the Ember.js git repo regarding a similar issue. Thanks Sam
