- From: chaals <notifications@github.com>
- Date: Wed, 03 Jun 2015 01:50:18 -0700
- To: w3c/editing <editing@noreply.github.com>
Received on Wednesday, 3 June 2015 08:50:45 UTC
Agreed we want to avoid a mess that makes implementation harder. But this is basically a user-facing option and it is unclear whether users will be really upset if it disappears. In particular, I don't know what the use cases are beyond "deal with someone pressing the insert button on a 1980s keyboard"… What about: 1. There is an event for a request to overtype, since there is a use behaviour on lots of systems that does this. 2. Expected behaviour is to say "we don't support that". 3. We note that some people *may* implement something different (such as allowing overtype mode). And FWIW I believe the "modern style" for APIs is to use strings rather than numerical constants as identifiers for things like events. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/55#issuecomment-108251545
Received on Wednesday, 3 June 2015 08:50:45 UTC