Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orion-dev] Browser-provided editor APIs

This idea at least sound great. I also heard it being mentioned during status call. But this would require at least one spec for that API, such that most browsers can adhere to. Is there any work/discussion group in this direction? Isn't relying on such an important browser feature critical for compatibility/portability? What is the Webkit opinion on this?

(Personally I am a fan of this idea.)


On Wed, Aug 10, 2011 at 9:34 PM, Kevin Dangoor <kdangoor@xxxxxxxxxxx> wrote:
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:

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?


Kevin Dangoor
product manager, developer tools


orion-dev mailing list

MSc Gabriel Petrovay
Mobile: +41(0)787978034

Back to the top