Make onChange work for contenteditable

Apparently it doesn’t, but it would be pretty awesome if it did. We already listen for DOMCharacterDataModified so I don’t think it should be too terrible. Tangentially it would be great to stop using mutation events and switch over to observers (let’s not do that here though unless it dovetails really nicely).

Interested @spicyj?

[gaearon]

Just checking in here to say a combination of onInput and a mutation observer covers modern browsers and IE11.

[willwhitney]

@edwardmsmith It may not work on older browsers, but for modern browsers you can use the onInput callback like so:

<div
  contentEditable="true"
  onInput={function(e) {
    console.log("woohoo!");
  }}
>initial content</div>

Edit: if you do that, be very sure not to use the app state for that ‘initial content’. That will make it a controlled component that gets rerendered every time, and the user’s cursor will jump to the beginning of the text with every keypress.