RDFElementImpl::ParseAttributeString() cannot return anything but kNameSpaceID_Unkown because the XML namespace scoping information is not properly set up in the element via the nsIXMLContent::SetContainingNameSpace() method. The net effect is that we can't properly match on both namespace and tag name; we only match tag name. This'll start to cause problems if people use the same tag name in different namespaces. Fixing this is not easy: currently, the XML namespace scoping information is lost during the translation from serialized XML into an RDF graph. We'll need to add some kind of table that stores this information. This gets even nastier in the face of duplicate resources in the same document, and aggregation. Anyway, it'll be a problem sometime...

Set target milestone to M5.

Set target milestone to M4 because of dependency from bug 4614.

So I talked with gramps and chofmann about this one. The additions to support this are starting to get pretty extensive, including whacking the XUL content sink, the XUL content model builder, and the tree builder. Per my discussion with gramps and chofmann, I am slipping these to M5, as well.

Fixed. Added code to the XUL content sink and the XUL content model builder to properly "pull" namespace decls through the graph. See dom-test-2.xul for verification.