Closed
Bug 45127
Opened 25 years ago
Closed 25 years ago
Wrong URL string used to construct kRDF_type object
Categories
(Core Graveyard :: Java APIs to WebShell, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: avm, Assigned: edburns)
Details
in rdf_util.cpp#123 the string "http://home.netscape.com/NC-rdf#" used
to get kRDF_type. But in Mozilla's rdf.h#55 the RDF_NAMESPACE_URI defined as
"http://www.w3.org/1999/02/22-rdf-syntax-ns#" ,
and used to get kRDF_type.
So, problems can appear when transfer kRDF_type between Webclient and Mozilla's
code, because they are differ.
I tried it with the other URL, and bookmarks no longer worked. I'm sticking
with #define NC_NAMESPACE_URI "http://home.netscape.com/NC-rdf#"
.
Marking invalid.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 3•25 years ago
|
||
Reopen.
Please look at the part of code of nsBookmarksService.cpp#230 :
...
gRDF->GetResource(NC_NAMESPACE_URI "Name", &kNC_Name);
gRDF->GetResource(NC_NAMESPACE_URI "ShortcutURL", &kNC_ShortcutURL);
gRDF->GetResource(NC_NAMESPACE_URI "URL", &kNC_URL);
gRDF->GetResource(RDF_NAMESPACE_URI "type", &kRDF_type);
gRDF->GetResource(RDF_NAMESPACE_URI "nextVal", &kRDF_nextVal)
...
and note that really two different URI's used to construct different resources:
"http://www.w3.org/1999/02/22-rdf-syntax-ns#" is used to get kRDF_type,
kRDF_nextVal, etc ...
and
"http://home.netscape.com/NC-rdf#" is used to get kNC_Name,kNC_URL, etc ..
But in webclient code (rdf_util.cpp) one "http://home.netscape.com/NC-rdf#"
is used to get ALL.
So from current point of view this bug is valid:
Wrong URL used to construct kRDF_type
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Fix checked in.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 5•24 years ago
|
||
Verified with JAVADEV_6_1_20010831.
Mark VERIFIED
Status: RESOLVED → VERIFIED
Updated•13 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•