getNamedItemNS (W3C DOM Core method)

Spec
Version Depr. Static
DOM2 No No
Browser support (more…)
IE7 FF1.5+ SA3+ OP9+
None Buggy Full Buggy
Returns
Node

Example

var attr = document.documentElement.attributes.getNamedItemNS
    ('http://www.w3.org/XML/1998/namespace', 'lang');

The example above retrieves a node called lang in the XML namespace, from the attributes collection of the documentElement. If it exists in the collection, the attr variable will be a reference to that node, otherwise it will be null.

Arguments

namespace (DOMString) required

The namespaceURI of the node to retrieve. A value of null means no namespace.

name (DOMString) required

The localName of the node to retrieve.

Description

Get a node with the specified local name and namespace URI from a NamedNodeMap.

Return value

A node (of any type) with the specified local name and namespace URI; or null if they don't identify a node in the map.

Compatibility

Internet Explorer Firefox Safari Opera
5.5 6.0 7.0 1.5 2.0 3.0 1.3 2.0 3.0 9.0 9.5
None None None Buggy Buggy Buggy Buggy Buggy Full Buggy Buggy

Internet Explorer doesn't implement this method (it returns undefined).

In Safari 1.3 and 2 attributes inherit a namespace from their owning element, therefore this method matches attributes with no explicit namespace if the namespace argument matches the default. They also treat an xml:lang attribute as a lang attribute, and therefore match it only if the namespace argument is http://www.w3.org/1999/xhtml (even when the document isn't any flavour of HTML). Other XML attributes which have no HTML analog (such as xml:space) are matched with their namespace correctly, but are also matched if the namespace argument is an empty string.

In Firefox an empty-string namespace is treated the same as a null namespace (ie. it's taken to mean no namespace, when it should be treated as a real namespace URI); conversely Opera only understands an empty string to mean no namespace, it doesn't understand null; the only browser to get this right is Safari 3.

: Behavior in HTML

Since namespaces are an XML construct, it's only reasonable to judge the behavior of this method in terms of XML (either on HTML pages in XHTML mode1, or pure XML). The behavioral variations of browsers in HTML mode2 are documented here for interest and reference, but the support summary table above does not consider this behavior.

All supported browsers in HTML mode behave essentially the same as they do in XHTML mode, except that they don't recognise namespaces at all. (So Opera only matches items in no namespace if the namespace argument is an empty string; Firefox only matches items in no namespace if the namespace argument is null or an empty string; Safari 3 only matches items in no namespace if the namespace argument is null; Safari 1.3 and 2 only match items in no namespace if the namespace argument matches the default.)

Footnotes

1 On XHTML pages served as application/xhtml+xml.

2 On XHTML or HTML pages served as text/html.

User-contributed notes

There are no comments yet.

Related Products