Skip to main content
deleted 3 characters in body
Source Link
Matt
  • 75.4k
  • 26
  • 156
  • 181

What they are saying is that objects that were Attr instances (e.g. such as those returned by Element.getAttributeNode()), used to have properties that it inherited from Node.

However, because this is not the case in DOM4, they are trying to remove this inheritance. Because of this, when you now get an instance of a Attr object, the properties listed in the depreciateddeprecated list will behave as they're documented.

The big question: It is depreciateddeprecated for an Attribute but is it for a Node too?: No, they are not depreciateddeprecated. You can see the list of properties Node has from it's own documentation page.

Attr objects aren't used much (ever?) anyway; are you sure this concerns you?

What they are saying is that objects that were Attr instances (e.g. such as those returned by Element.getAttributeNode()), used to have properties that it inherited from Node.

However, because this is not the case in DOM4, they are trying to remove this inheritance. Because of this, when you now get an instance of a Attr object, the properties listed in the depreciated list will behave as they're documented.

The big question: It is depreciated for an Attribute but is it for a Node too?: No, they are not depreciated. You can see the list of properties Node has from it's own documentation page.

Attr objects aren't used much (ever?) anyway; are you sure this concerns you?

What they are saying is that objects that were Attr instances (e.g. such as those returned by Element.getAttributeNode()), used to have properties that it inherited from Node.

However, because this is not the case in DOM4, they are trying to remove this inheritance. Because of this, when you now get an instance of a Attr object, the properties listed in the deprecated list will behave as they're documented.

The big question: It is deprecated for an Attribute but is it for a Node too?: No, they are not deprecated. You can see the list of properties Node has from it's own documentation page.

Attr objects aren't used much (ever?) anyway; are you sure this concerns you?

Source Link
Matt
  • 75.4k
  • 26
  • 156
  • 181

What they are saying is that objects that were Attr instances (e.g. such as those returned by Element.getAttributeNode()), used to have properties that it inherited from Node.

However, because this is not the case in DOM4, they are trying to remove this inheritance. Because of this, when you now get an instance of a Attr object, the properties listed in the depreciated list will behave as they're documented.

The big question: It is depreciated for an Attribute but is it for a Node too?: No, they are not depreciated. You can see the list of properties Node has from it's own documentation page.

Attr objects aren't used much (ever?) anyway; are you sure this concerns you?