Closed
Bug 279078
Opened 20 years ago
Closed 20 years ago
XML Error reporting confusing since Expat landing
Categories
(Core :: XML, defect, P2)
Core
XML
Tracking
()
RESOLVED
FIXED
mozilla1.8beta1
People
(Reporter: bzbarsky, Assigned: peterv)
Details
Attachments
(1 file, 1 obsolete file)
3.28 KB,
patch
|
bzbarsky
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
Load the attached testcase (which happens to be invalid XML).
ACTUAL RESULTS: Error message says:
XML Parsing Error: mismatched tag. Expected: </htpp://goo/?aaa>.
EXPECTED RESULTS: Error message that says:
XML Parsing Error: mismatched tag. Expected: </aaa>.
or something along those lines (what it was pre-Expat landing).
It looks like we're dumping the whole string we got from expat, complete with
the U+FFFF (that's the '?' char) out in this error. We should probably not do
that.....
Assignee | ||
Updated•20 years ago
|
Priority: -- → P2
Target Milestone: --- → mozilla1.8beta
Assignee | ||
Comment 1•20 years ago
|
||
Also fixes bug 205561.
Attachment #171879 -
Flags: superreview?(bzbarsky)
Attachment #171879 -
Flags: review?(bzbarsky)
Reporter | ||
Comment 2•20 years ago
|
||
Comment on attachment 171879 [details] [diff] [review]
v1
>+ // Since this'll use |white-space: pre;| a tab equals 8 spaces.
Is that true? What about the string
" \t"
? I'd expect the tab to equal 6 spaces, then... Test?
>+ * Expat can send the following:
Why not just use SplitExpatName here? It'll do a bit of extra work (you'll
have to grab the strings from inside the atoms). But this is not
perf-sensitive, and not duplicating code is worth it, I think.
Assignee | ||
Comment 3•20 years ago
|
||
(In reply to comment #2)
> (From update of attachment 171879 [details] [diff] [review] [edit])
> >+ // Since this'll use |white-space: pre;| a tab equals 8 spaces.
>
> Is that true? What about the string
>
> " \t"
>
> ? I'd expect the tab to equal 6 spaces, then... Test?
You're right, I misread the CSS spec. :-/
> Why not just use SplitExpatName here? It'll do a bit of extra work (you'll
> have to grab the strings from inside the atoms). But this is not
> perf-sensitive, and not duplicating code is worth it, I think.
It's not really possible until we either link the parser into layout, or we
move the error reporting into content. Both are non-trivial, so I'd like to
keep my patch for now.
Attachment #171879 -
Attachment is obsolete: true
Attachment #171924 -
Flags: superreview?(bzbarsky)
Attachment #171924 -
Flags: review?(bzbarsky)
Assignee | ||
Updated•20 years ago
|
Attachment #171879 -
Flags: superreview?(bzbarsky)
Attachment #171879 -
Flags: review?(bzbarsky)
Reporter | ||
Comment 4•20 years ago
|
||
Comment on attachment 171924 [details] [diff] [review]
v1.1
r+sr=bzbarsky
Attachment #171924 -
Flags: superreview?(bzbarsky)
Attachment #171924 -
Flags: superreview+
Attachment #171924 -
Flags: review?(bzbarsky)
Attachment #171924 -
Flags: review+
Assignee | ||
Updated•20 years ago
|
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•