1426966 - Element.innerHTML documentation is incorrect

Status: RESOLVED FIXED

(Developer Documentation Graveyard :: API: DOM, defect, P1)

Description

[isaacaaron79]

What did you do?
================
1. 
2. 
3. 

What happened?
==============

Some parts of the specification summary in Mozilla are incorrect and the example is wrong too. A thorough review should be made. One of the errors I mention below:

All the internet version, including Edge, when writing in the textarea element any word, the innerHTML property changes automatically. In Gecko NO (the initial value remains).
The input NEVER RETURNS ANYTHING in any browser or version, changes its value, but that's it, just that, not the value of the innerHTML property, which does not store anything.

This explanation of this property in mozilla is wrong.

Mozilla Summary:

This property was initially implemented by web browsers, then specified by the WHATWG and W3C in HTML5. Old implementations may not all implement it exactly the same way. For example, when text is entered into a text input, Internet Explorer changes the value attribute of the input's innerHTML property but Gecko browsers do not.

What should have happened?
==========================
Internet Explorer DOES NOT CHANGE the value of the innerHTML or Gecko property, the innerHTML property of the input text element DOES NOT RETURN ANYTHING. That's why the explanation is wrong and I should say:

When the text is entered into a multi-line text box (textarea), Internet Explorer will change the value of the innerHTML property of the textarea element, while the Gecko browsers do not.


Is there anything else we should know?
======================================
a complete revision of the article.
The section note at the beginning of the document does not correspond to reality either. As it happens in all the elements, apart from what the note says.

Comment 1

[isaacaaron79]

For me the specification in mozilla is incorrect and I refer to what I have said.

What do you think?

Comment 2

[isaacaaron79]

¿?

Comment 3

[isaacaaron79]

Florian Scholz what do you mean by Priority: - → P1, am I new here? I see that nobody says anything.

Comment 4

[Eric Shepherd [:sheppy]]

I have largely rewritten this page, removing incorrect information, adding new material, replacing examples that didn't work, etc. Please let me know if this resolves all your concerns.

Comment 5

[isaacaaron79]

I'll review it and tell you. In the publication in Spanish modify erroneous information publish improvements.

Comment 6

[Eric Shepherd [:sheppy]]

Setting the needinfo flag again for the reporter to help remind to get back to me after checking this.

Comment 7

[Eric Shepherd [:sheppy]]

OK, going to call this finished. Hurray!

Comment 8

[isaacaaron79]

Yes, it can be terminated. As I mentioned in the previous message that I see that does not come out here, I reviewed everything, and I see it correct after the modification.

Comment 9

[isaacaaron79]

Hi Eric Shepherd, what does not convince me yet is the note at the beginning of the article:

Note: If a <div>, <span>, or <noembed> node has a child text node that includes the characters (&), (<), or (>), innerHTML returns these characters as the HTML entities "& amp; "," & lt; " and "& gt;" respectively. Use Node.textContentto get a raw copy of these text nodes' contents.


If you do tests you will see that not only happens with <div>, <span>, or <noembed> but, with any element.