搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

opening Firefox displays xml parsing error

  • 8 个回答
  • 1 人有此问题
  • 25 次查看
  • 最后回复者为 jon_joy_1999

more options

I'm using Firefox on a Samsung moto G6 with Android 9. When I open Firefox it displays a yellow page that says XML Parsing Error: no root element found. Location: chrome://geckoview/content/geckoview.xhtml line number 1, column 1.

I can't open any pages. I've tried restarting my device but I still get the message. What should I do?

I'm using Firefox on a Samsung moto G6 with Android 9. When I open Firefox it displays a yellow page that says XML Parsing Error: no root element found. Location: chrome://geckoview/content/geckoview.xhtml line number 1, column 1. I can't open any pages. I've tried restarting my device but I still get the message. What should I do?

被采纳的解决方案

Hi

I have looked into this one a bit further and have found that our developers are aware of this issue. You can follow progress on this work and add comments at:

https://bugzilla.mozilla.org/show_bug.cgi?id=1668842

定位到答案原位置 👍 1

所有回复 (8)

more options

Hi

Do you have any add-ons installed in Firefox for Android?

more options

I don't believe I have any add-ons installed. When I go to Addons in Firefox I'm presented with a list of items, all with a + box.

由jon_joy_1999于修改

more options

What is the address of the website that you are trying to view?

more options

It was all websites. Google, Wikipedia, Slate, the Support button in the About menu for Firefox all gave me this error.

more options

Is this a version of Firefox for Android that you have installed from the Google Play store?

more options

Yes. I installed it a few months ago from Google Play store.

more options

选择的解决方案

Hi

I have looked into this one a bit further and have found that our developers are aware of this issue. You can follow progress on this work and add comments at:

https://bugzilla.mozilla.org/show_bug.cgi?id=1668842

more options

Thanks for the information Seburo. I just tested the browser again on that phone and the issue seems to have resolved itself. But if it happens again I'll use this to try to provide more information to bugzilla.