V0 Google Translate DOM Conflict

Feedback
1

Bug Report: Google Translate DOM Conflict

Hi team,

I wanted to report a bug I discovered that might affect other users. This isn’t a support request - just letting you know about the issue so it can be addressed for the broader community.

Steps to Reproduce:

  1. Have Google Translate “Always translate to English” enabled in Chrome
  2. Change website language to Japanese
  3. Error appears in console: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

Expected Behavior:

  • Page should translate smoothly without DOM errors

Current Behavior:

  • Console shows node removal error
  • Error persists until user disables “Always translate to English” in Chrome settings

Environment:

  • Platform: Vercel
  • Browser: Google Chrome
  • Google Translate: Always translate to English enabled

Additional Notes:

  • Error occurs consistently when changing language
  • Issue affects any user with automatic translation enabled in Chrome
  • Users need to manually disable the “Always translate” feature to stop the error

Just flagging this for your awareness to help improve the platform experience for Chrome users who rely on automatic translation.

Best regards, Josh

2

Thanks for sharing this bug report, @spiritual! I’ll pass onto the v0 team. :saluting_face:

3

I encountered the same problem. As soon as I opened Google Translate to translate English into Chinese, the Vercel page would display “Error loading dashboard”. console: NotFoundError: Failed to execute ‘insertBefore’ on ‘Node’: The node before which the new node is to be inserted is not a child of this node.

4

Thanks for sharing! Passing on this feedback :pray:

5

Hi, folks! This should now be fixed. :slight_smile: