I can't remember where the discussion took place, and google and github didn't help me either. But regarding this pull request, the question is: what would you do with this functionality. As far as I can see contenteditable really has no purpose in a driver which doesn't support JavaScript. contenteditable elements aren't treated as form elements, and thus aren't submitted along with form data.

I tried really hard to come up with a case where changing an element due to it having contenteditable would cause any kind of effect at all in the absence of JavaScript, and the only thing I could come up with is something like this:

I agree it makes no sense in drivers that don't support JS (other than uniformity maybe) but it does make sense for the JS drivers. Looking at the head it doesn't look like the selenium driver would support it as set doesn't do anything for element's it doesn't know how to manipulate, and content-editable is never mentioned, so you'd have to drop down to native and send_keys yourself... which makes me sad...

I'd be open to writing some tests for and making it work on selenium if the behaviour is agreeable but as the previous two PR's with this functionality have been rejected and I'm using a different driver anyway (poltergeist)...

@JonRowe I'm working on a major refactor of the test suite, which will affect how these tests would be written. I should be able to finish that up in the next couple of days. I'd suggest holding off until then, if you're interested in making this work in Selenium.