After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 351296 - XML parsing error in error page for resuming from crash
XML parsing error in error page for resuming from crash
Status: RESOLVED FIXED
Product: epiphany
Classification: Core
Component: General
2.14.x
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2006-08-14 14:02 UTC by Matthew Paul Thomas (mpt)
Modified: 2006-08-21 19:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthew Paul Thomas (mpt) 2006-08-14 14:02:53 UTC
Epiphany 2.14.3, Ubuntu 6.06

Upon restarting Epiphany after a crash, one window showed a yellow Gecko XML error:

XML Parsing Error: not well-formed
Location: https://launchpad.net/products/launchpad/+bugs?field.searchtext=product+page&orderby=-importance&search=Search&field.status%3Alist=Unconfirmed&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&field.status%3Alist=Needs+Info&field.status%3Alist=Fix+Committed&field.assignee=&field.owner=&field.omit_dupes=on&field.has_patch=&field.has_no_package=
Line Number 27, Column 98:<p>The page “https://launchpad.net/products/launchpad/+bugs?field.searchtext=product+page&orderby=-importance&search=Search&field.status%3Alist=Unconfirmed&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&field.status%3Alist=Needs+Info&field.status%3Alist=Fix+Committed&field.assignee=&field.owner=&field.omit_dupes=on&field.has_patch=&field.has_no_package=” in this tab was not fully loaded yet when the web browser crashed; it could have caused the crash.</p>
-------------------------------------------------------------------------------------------------^

It seems that any "&" character in the URL isn't being escaped.
Comment 1 Christian Persch 2006-08-21 19:24:01 UTC
Fixed in the development version. The fix will be available in the next major release. Thank you for your bug report.

Fixed in CVS. The fix will go into the next patch release. Thank you for your bug report.