Closed
Bug 322570
Opened 20 years ago
Closed 20 years ago
Namespaces that are not used don't get registered
Categories
(Core :: XML, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: bzbarsky, Assigned: sicking)
References
Details
(Keywords: regression)
Attachments
(2 files)
165 bytes,
application/xml
|
Details | |
1.19 KB,
patch
|
bzbarsky
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
Since bug 192139, when parsing XML we only call RegisterNamespace from SplitExpatName, so a namespace that's not actually used in the document doesn't get registered with the namespace manager. This causes us to have a bug in lookupPrefix, as far as I can see.
![]() |
Reporter | |
Comment 1•20 years ago
|
||
Assignee | ||
Comment 2•20 years ago
|
||
Yeah, this should be fixed in the lookupPrefix implementation
![]() |
Reporter | |
Comment 3•20 years ago
|
||
So should ResolvePrefix just call RegisterNamespace on the string you pass in or something? That seems a little suboptimal...
In general, it also looks like the namespace manager hashtables could balloon uncontrollably. :(
Assignee | ||
Comment 4•20 years ago
|
||
The entire lookup is unneccesary. It seems like it was originally some sort of optimization to bail early, but it's obviously wrong. Patch comming up.
Assignee | ||
Comment 5•20 years ago
|
||
Assignee: peterv → bugmail
Status: NEW → ASSIGNED
Attachment #207773 -
Flags: superreview?(bzbarsky)
Attachment #207773 -
Flags: review?
Assignee | ||
Updated•20 years ago
|
Attachment #207773 -
Flags: review? → review?(bzbarsky)
![]() |
Reporter | |
Comment 6•20 years ago
|
||
Comment on attachment 207773 [details] [diff] [review]
This otta' do it
Sure.
Attachment #207773 -
Flags: superreview?(bzbarsky)
Attachment #207773 -
Flags: superreview+
Attachment #207773 -
Flags: review?(bzbarsky)
Attachment #207773 -
Flags: review+
Assignee | ||
Comment 7•20 years ago
|
||
Checked in
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•