Why has innerHTML not been added to the w3c specs?

Is there any particular reason that it isn't in any of the the specs?

It seems to be supported in all browsers, (although I'll a开发者_如何学Godmit it doesn't work right in all of them...since you have to use libraries like innerXHTML to get it to work right thanks to Internet Explorer.

Is innerHTML in danger of disappearing from forthcoming versions of browsers? If not shouldn't they just add it already?

I'm marking this community wiki as I know I'm gonna take a beating on my rep for this...but I just wondered why...

http://dev.w3.org/html5/spec/Overview.html#innerhtml

There's absolutely no way it's in danger, thousands of applications rely on it and doing so would be a horrible idea.

I'll admit it doesn't work right in all of them...since you have to use libraries like innerXHTML to get it to work right thanks to Internet Explorer.

IE invented innerHTML; you can't really expect it to work any better than it does there.

Is there any particular reason that it isn't in any of the the specs?

It's proposed for HTML5, for what it's worth. There is certainly no danger of it disappearing in the future, though you should continue to use it only for the simple cases where you are writing straight ‘block’ or ‘inline’ element content. Special cases like tables and selects are going to continue to be troublesome.

IE, being the inventor of dynamically modifying the content has gone with it all the way - other browsers didn't!

Passing the string as innerHTML means that the string will get through a normalization process before it gets passed to the element. Meaning it will get transformed fom a string into a proper html parsing content.

Firefox implemented it wrongly. It doesn't distinguish between html:innerHTML and html:innerText and plain string:text. The difference is literally obvious for IE, but not for FF. Hence the difference in handling situations and the confusion of FF only coders when they go back to the master.