parseXULToFragment needs to handle non-well-formed XML
Categories
(Toolkit :: UI Widgets, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox72 | --- | fixed |
People
(Reporter: WeirdAl, Assigned: WeirdAl)
References
()
Details
Attachments
(1 file)
I accidentally passed some not-well-formed XML (specifically, forgetting to replace & with & in a URL string) into MozXULElement.parseXULToFragment. The error I got back was not helpful:
JavaScript error: , line 0: uncaught exception: Object
If you do this, the DOMParser will return a <parsererror>...</parsererror> document, but one without a XUL box root element. Then it reaches the selectNodeContents(null) line and throws an exception.
Testcase coming.
| Assignee | ||
Comment 1•6 years ago
|
||
| Assignee | ||
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Comment 3•6 years ago
|
||
Backed out changeset 8799781bbf34 (bug 1591761) for causing mass test failures.
Push that started the failures: https://treeherder.mozilla.org/#/jobs?repo=autoland&resultStatus=superseded%2Ctestfailed%2Cbusted%2Cexception%2Crunnable&revision=8799781bbf3490a6f8c58c7de511dac360be6bb5&selectedJob=273367148
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=273367148&repo=autoland&lineNumber=1090
Backout: https://hg.mozilla.org/integration/autoland/rev/a09c768d2dc0649a82c15788e5a33052616d7f16
| Assignee | ||
Comment 4•6 years ago
|
||
One of the changes in the Phabricator request was both unnecessary and broke the parseXULToFragment code. Fixed.
Comment 6•6 years ago
|
||
| bugherder | ||
Comment 7•6 years ago
|
||
| bugherder landing | ||
Description
•