Bug 52049 - XML Parser reports a parsing error with wrong column number
Summary: XML Parser reports a parsing error with wrong column number
Status: UNCONFIRMED
Alias: None
Product: WebKit
Classification: Unclassified
Component: XML (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-07 01:31 PST by Joone Hur
Modified: 2011-01-07 10:27 PST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joone Hur 2011-01-07 01:31:00 PST
When Firefox loads LayoutTests/fast/parser/xhtml-alternate-entities.xml, it reports a parsing error as follow:

"XML Parsing Error: undefined entity
Location: file:///Users/joone/git/WebKit/LayoutTests/fast/parser/xhtml-alternate-entities.xml
Line Number 4, Column 7: 

<h1> &fnof;&auml;&iuml;&Iuml; </h1> <!-- If you get a parse error, this test has PASSED. -->
------^ "

In case of WebKit based browsers, you can see the following error,

"This page contains the following errors:

error on line 4 at column 13: Entity 'fnof' not defined
Below is a rendering of the page up to the first error."

Actually, there is entity 'auml' at column13, so it seems to be wrong information. 
On the other hand, Firefox seems to report exact information.
Anyway, I think LibXML2 may have a problem to report parsing errors.
Comment 1 Patrick R. Gansterer 2011-01-07 07:43:55 PST
Is there a spec how to report XML errors?
FF reports the first character of the entity, libxml2 the last. So I don't think there's a problem.

If you think this is a bug you should report it at the libxml2 bugtracker, because WebKit only shows the error message of the parser library.

BTW: IE throws a system error and Opera interprets the it as normal characters.