Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Learn More

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

  • 2 ответа
  • 40 имеют эту проблему
  • 4 просмотра
  • Последний ответ от the-edmeister

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

Выбранное решение

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...

Прочитайте этот ответ в контексте 👍 0

Все ответы (2)

more options

Выбранное решение

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...

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!