Re: [editing] set targetRange to null for all editTypes where the targetRange would always have been equal to the selection range (#80)

@rniwa @kojiishi: At the CSSWG @frivoal and I discussed whether it would be good enough that it is specifies the order of the different events related to user input within cE are synchronous, if we want to make sure that the selection/caret has not changed at the time the event is being triggered, and also to be able to do the timeout-0 type polyfills @rniwa was contemplating.

The synchronous nature of the events mean that one of them has to finish before the next one starts, right? Does it also ensure that there cannot be a separate thread that changes the selection in the meantime? 

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/80#issuecomment-136451193