Closed Bug 102534 Opened 24 years ago Closed 24 years ago

typedNode serialization doesn't handle default namespace correctly

Categories

(Core Graveyard :: RDF, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
mozilla0.9.5

People

(Reporter: tingley, Assigned: tingley)

Details

Attachments

(1 file)

My fix for bug 97775 handles default namespaces in a bogus way -- it will generate things that look like this: <:channel> <foo:prop>14</foo:prop> </:channel> This is because for default namespace, |MakeQName()| will return success, but |aNameSpacePrefix| will contain the empty string. We need a check for this when actually writing out the RDF. http://lxr.mozilla.org/seamonkey/source/rdf/base/src/nsRDFXMLSerializer.cpp#488
-> me
Assignee: waterson → tingley
Status: NEW → ASSIGNED
Attached patch fixSplinter Review
Proposed solution: suck less and check for an empty namespace. Waterson, Shaver: any chance you could take a look at this? I'd like to get this in for 0.9.5 since it's sort of a regression (as in, we used to handle this ok, now we don't). Thanks.
Keywords: patch, review
Target Milestone: --- → mozilla0.9.5
Comment on attachment 51534 [details] [diff] [review] fix zoiks! r/sr=waterson
Attachment #51534 - Flags: superreview+
Comment on attachment 51534 [details] [diff] [review] fix r=shaver. Nice catch.
Attachment #51534 - Flags: review+
I'll get this checked in today.
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
tever is not RDF QA anymore
QA Contact: tever → nobody
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: