Firefox bug - XML Parsing Error: unexpected parser state
I received the following error while browsing a certain website:
XML Parsing Error: unexpected parser state
Location: jar:file:///TorBrowser/FirefoxPortable/App/Firefox/omni.ja!/chrome/toolkit/content/global/netError.xhtml
Line Number 308, Column 50:
<div id="ed_netReset">&netReset.longDesc;</div>
-------------------------------------------------^
Unfortunately, I cannot provide the URL at which this error appeared.
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
Trac:
Cc: N/A to g.koppen@jondos.de- Author
I have now also received the following error:
XML Parsing Error: unexpected parser state Location: jar:file:///TorBrowser/FirefoxPortable/App/Firefox/omni.ja!/chrome/toolkit/content/global/netError.xhtml Line Number 304, Column 68: <div id="ed_connectionFailure">&connectionFailure.longDesc;</div> -------------------------------------------------------------------^
This is very likely an underlying Mozilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=569229
Trac:
Cc: g.koppen@jondos.de to gkTrac:
Keywords: N/A deleted, tbb-firefox-patch addedTrac:
Owner: mikeperry to tbb-team
Component: Firefox Patch Issues to Tor BrowserMarked #17447 (moved) as a duplicate.
Trac:
Cc: gk to gk, arma
Sponsor: N/A to N/A
Severity: N/A to NormalStill not fixed in ESR45... On Windows 7 with TBB 6.0a3 (and earlier) there is only one string in Console:
unexpected parser state aboutNetError.xhtml:388:68
orunexpected parser state aboutNetError.xhtml:389:54
orunexpected parser state aboutNetError.xhtml:395:58
But from the user's side it looks bad:Trac:
Reviewer: N/A to N/A
Summary: TorBrowser: XML Parsing Error to Firefox bug - XML Parsing Error: unexpected parser stateSTR? (TBB 6.5a2) http://ehlznccisf5mnhw2.onion/test.php
unexpected parser state aboutNetError.xhtml:447:68
or
unexpected parser state aboutNetError.xhtml:451:50
Folks on #tor report that the bug mentioned in comment:3 got fixed by Mozilla and it is planned to ship the fix in Firefox 53. That's a bit late for us which is why I have asked to get it uplifted to Aurora. Tracking for our ESR 52 switch.
Trac:
Keywords: N/A deleted, ff52-esr addedTrac:
Keywords: ff52-esr deleted, ff52-esr-will-have addedThis will be fixed in 7.0a3 which is based on Firefox 52 ESR.
Trac:
Resolution: N/A to fixed
Status: new to closed- Trac closed
closed
- Georg Koppen mentioned in issue #9171 (closed)
mentioned in issue #9171 (closed)
- Georg Koppen mentioned in issue #9294 (moved)
mentioned in issue #9294 (moved)
- Georg Koppen mentioned in issue #9999 (closed)
mentioned in issue #9999 (closed)
- Georg Koppen mentioned in issue #17447 (moved)
mentioned in issue #17447 (moved)
- cypherpunks mentioned in issue #21887 (moved)
mentioned in issue #21887 (moved)