|Re: [orion-dev] Browser-provided editor APIs|
Le Thu, 11 Aug 2011 21:23:38 +0300, Silenio Quarti
<Silenio_Quarti@xxxxxxxxxx> a écrit:The idea I have at the moment would be to provide additional API for
Improving the basic editing support on the browser would be much
I agree with you that currently contentEditable is the only way to support
a10y, i18n, input method and bidi. But contentEditable does not handle
well large documents. This forced us to virtualize its content and
overwrite some of the default editing behavior provide by the browser.
Is your goal to provide a text widget (perhaps extending contentEditable)
or to provide basic API to support implementing a text widget? If the
latter, these are some of the areas that we found difficulties because of
the lack of API on the browsers:
contentEditable-based editors to aid the development of web-based (source)
These ideas are really based on the integration work I did for Orion into
Firefox. Please note that there are no plans made yet, we just want to
start the discussion going, to eventually reach some conclusions and
implement some new APIs we could expose to the web.We should probably focus on the most important API at first. A too ambitious plan, an all-encompassing plan can get across much slower and harder.
- clipboard support
- hit testing (bidi aware)
- cursor movement (complexe scripts aware, ie. Thai)
- full selection
- selection (bidi aware. ie. split cursors)
What would you consider as the most important first steps?
I'll also try to come up with some ideas.
orion-dev mailing list
Back to the top