| [orion-dev] Browser-provided editor APIs |
| Editors like Orion have to go to a lot of trouble to implement basic editing behavior. The problem is that even with all of that trouble taken, bidi text and accessibility are not easily supported (if at all!). I know that Orion is taking the approach of leveraging contentEditable where possible, but I also know that Orion is going to great lengths to get there: https://bugzilla.mozilla.org/show_bug.cgi?id=660784#c15 Meanwhile the built-in editing code in browsers like Firefox already know how to do a10y and bidi text. What if basic editing could be provided by the browser and higher-level (code oriented, in Orion's case) functionality could be added on top? We can make it happen. We just need to figure out what the APIs should be (and this is where people building the core editor code can help!) What APIs would you want to outsource basic caret movement, selection and typing behavior to the browser? https://wiki.mozilla.org/Features/Desktop/EditorAPI Kevin -- Kevin Dangoor product manager, developer tools work: http://mozilla.com/ blog: http://blueskyonmars.com/ @dangoor |