We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Wo archive tread sia. Meɖekuku bia biabia yeye ne ehia kpeɖeŋu.

I get the following error everytime a new window opens: xmlnode.getelementsbytagname("id")[0].firstchild is null - 1 Can anyone please help?

  • 2 ŋuɖoɖowo
  • 40 masɔmasɔ sia le wosi
  • 4 views
  • Nuɖoɖo mlɔetɔ the-edmeister

AnonymousUser
AnonymousUser
more options

I am using XP home edition. This comes up in a Javascript application window every time a new window opens in FF. I do not get this error in IE. I can open other tabs in FF and they are fine, just not other windows. Thank you very much for any help!

This happened

Every time Firefox opened

I am using XP home edition. This comes up in a Javascript application window every time a new window opens in FF. I do not get this error in IE. I can open other tabs in FF and they are fine, just not other windows. Thank you very much for any help! == This happened == Every time Firefox opened

Ŋuɖoɖo si wotia

Do you have that problem when running in the Firefox SafeMode? http://support.mozilla.com/en-US/kb/Safe+Mode Don't select anything right now, just use "Continue in SafeMode."

If not, see this: http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+theme...

Xle ŋuɖoɖo sia le goya me 👍 0

All Replies (2)

the-edmeister
the-edmeister
  • Moderator
more options

Ɖɔɖɔɖo si wotia

Do you have that problem when running in the Firefox SafeMode? http://support.mozilla.com/en-US/kb/Safe+Mode Don't select anything right now, just use "Continue in SafeMode."

If not, see this: http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+theme...

AnonymousUser
AnonymousUser Biabia la
more options

Thank you very much!! You were right on with your advice. It was an add-on so I just uninstalled it and the error went away. Thanks again!