Skip to main content

Fixing the “removeChild could not be executed on Node” Error

Learn how to fix the "removeChild" error in Songer by adjusting Chrome's auto-translate settings.

If you've seen this error while using Songer, you're not dealing with a bug in the platform itself. The culprit is your browser's built-in auto-translate feature. When it's active, it interferes with how Songer loads certain page elements, and that conflict throws this error. It happens most often when you're working on custom songs, but it can show up in other parts of the platform, too.

The fix doesn't require any technical knowledge. It's two steps in your browser settings and takes about 20 seconds.

Steps to Fix “removeChild" Error

In Chrome (also Edge, Opera, Brave, and other Chromium browsers):

  1. Open your browser settings and go to Languages

  2. Scroll down and toggle off "Use Google Translate" (in Edge, it's called "Offer to translate pages that aren't in a language I read")

In Firefox:

  1. Open Firefox Settings and go to AI Controls

  2. Under "On-device AI," find Translations and set it to Blocked

In Safari:

  1. If a page is currently translated, click the translate icon in the address bar and choose "View Original"

  2. Avoid selecting "Translate to..." on Songer pages going forward

Use Songer's built-in language selector in the top right corner of the page to set your preferred language instead.

That's the full fix. Once auto-translate is off, your browser stops interfering with how the page loads, and the error stops appearing. Songer's own language selector handles everything you'd need auto-translate for anyway, so you're not losing anything by turning it off.

If the error comes back, double-check that your browser didn't re-enable auto-translate after an update. It occasionally resets certain settings on its own.

Did this answer your question?