Re: [editing-explainer] How should custom controls declare their Responsive Input mapping? (#18)

We could also just drop the formatting events entirely, at least for contentEditable=Typing. That would remove the need to change bindings and simplify everything a fair bit. Otherwise this seems as somewhat of a reinvention of execCommand("bold") which never really worked for the end user anyway. If there is a button to bolden things, the clock event can tell the user Javascript about that and set it up so that that triggers the same function that already is bound to CTRL+B.

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