Re: [editing] How do we switch the caret between overtype and insert mode? (#55)

> Do I understand correctly that on Windows/Linux overtype is a system-wide feature that applies to any input?

Indeed, it works just about everywhere and it works in contenteditable. An exception are text input boxes like the github one I'm typing in right now, that were built from the ground up in JavaScript where the authors of that particular JS library decided not to support it.

> On typing container, that could be something like `setInputMode()`. For multiple reasons, I’d stick with DOM conventions and pass predefined numeric constants as mode identifiers (`INSERT_MODE` and `OVERTYPE_MODE` or something); but we’ve got no namespace to put those constants in. (You may argue that namespace for two constants is an overkill, and I’d probably agree.)

Sure, what's your suggestion to do then?


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