- From: Johannes Wilm <notifications@github.com>
- Date: Wed, 13 Apr 2016 13:41:50 -0700
- To: w3c/editing <editing@noreply.github.com>
- Message-ID: <w3c/editing/issues/118/209639384@github.com>
@choniong I found the resolution [1]. And it does make sense: We were mainly looking at cE=typing. cE=typing is a contenteditable mode where the browser would only handle typing new characters and selection changes. It will not handle deletion of content. The exception here being during composition. During composition, the browser would have a default behavior both for insertion and deletion of characters, because at the time we understood the relationship of IME and browser as making it impossible for the browser to hinder IME input. So given that the deletion of the compositionstring (in point 5) is something that cannot be canceled and will ave to have a Dom changing action on cE=typing, I would say this has to be deleteComposedCharacter. [1] "RESOLUTION: : We will have typing with compositionstart (cancelable) when you can set a selection point, then a series on non cancelable beforeinputs to replace text, and two kinds of delete events - one inside composition not cancelable, and a "normal" one to be handled by the application" https://www.w3.org/2015/08/23-webapps-minutes.html --- 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/118#issuecomment-209639384
Received on Wednesday, 13 April 2016 20:42:20 UTC