Re: [w3c/editing] contentEditable: clarification of selection and typing behavior (#156)

Personally I am still a bit torn whether or not this is important. The replacement of the existing DOM content will in most cases be something the JS editor will want to control. JS editors also tend to not like it when selections change "automagically" because the browser thinks this is a good idea.

On the other hand, the selections should probably be the same. And if doing roughly the same thing in different browsers leads to entirely different selections, the JS editor will need to spend more time trying to standardize these selections before action on the insertion of new content.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/156#issuecomment-263835729