Closed
Bug 58229
Opened 24 years ago
Closed 23 years ago
XML content and parser error displayed in the same window
Categories
(Core :: XML, defect, P3)
Core
XML
Tracking
()
VERIFIED
WORKSFORME
Future
People
(Reporter: hjtoi-bugzilla, Assigned: hjtoi-bugzilla)
Details
(Keywords: polish)
Attachments
(1 file)
Trivial bug, try to open an XML document without a stylesheet that is missing an end tag. You will get this error message: This XML document is a missing a end tag for the root element. The "a" should be "an".
Assignee | ||
Comment 1•24 years ago
|
||
Trivial, taking ;)
Assignee: nisheeth → heikki
Whiteboard: [fixinhand]
Target Milestone: --- → mozilla0.8
Assignee | ||
Comment 2•24 years ago
|
||
Doh, we no longer get that error message. Instead we get XML Parsing Error: no element found so I am marking this as worksforme.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 3•24 years ago
|
||
Comment 4•24 years ago
|
||
Open the test case in N6. Two things should be displayed in the browser window: the document's content and a parser error. Usually, if the document is not well-formed ,you get a parser error only. No content of the document should be displayed. But in this case, you get both.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 5•24 years ago
|
||
Changing summary to reflect issue.
Summary: Typo in XML parser error (a end tag -> an end tag) → XML content and parser error displayed in the same window
Assignee | ||
Updated•24 years ago
|
Whiteboard: [fixinhand]
Target Milestone: mozilla0.8 → ---
Assignee | ||
Comment 6•24 years ago
|
||
Since this bug mutated, changing milestone and whiteboard.
Assignee | ||
Comment 7•24 years ago
|
||
This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug,or if it blocks your work in some way -- please attach your concern to the bug for reconsideration.
Comment 8•23 years ago
|
||
This bug seems to have gotten fixed, as I only see the parser error while displaying petersen's testcase in my 2002011508 build. Marking WFM.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 23 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•