It would be interesting to see what t.toString() returns, or just do alert(t) or something similar. If it's truly an XPConnect object, you'll get some information as to that. Also look at the JSConsole and see if you're getting any errors reported. You might be running into a security issue, but you should see some errors for that.
[xpconnect wrapped (nsISupports, nsIRDFNode, nsIRDFLiteral) @ 0x87df408] [xpconnect wrapped nsIRDFNode @ 0x8194bd8]
When I see the first, the code works. With the second, t.Value is undefined, I don't see a javascript error so t.Value does exist.
What you say here does not follow. An attempt to access a property that does not exist yields 'undefined' and does *not* cause an error.
I am using a chrome uri so there shouldn't be a security problem.
I have written a small program which illustraits my problem, I posted it to netscape.public.mozilla.rdf earlier today, it is only about 1.5k. I posted some code a couple of days ago as well, it is less interesting though.
I attempted to address your question in your thread in the RDF newsgroup. I think you are most likely running afoul of an assumption that xpconnect knows more about your object than it does.
When in doubt call QueryInterface.
John.
