Re: intro

On Tue, Jun 24, 2014 at 11:15 AM, Robin Berjon <robin@w3.org> wrote:

> Hi Johannes,
>
> welcome!
>
> thanks!

<snip>


> If you have specific examples of things that have been particularly
> painful (or downright impossible), we're certainly interested in hearing
> about them so that we can take them into account.


There are many frustrating aspects to it, but the #1 frustrating issue
(that cannot be resolved on the side of Javascript without growing one's
own cursor) is: Places that the cursor cannot go. Before, after and
in-between SVGs, Canvas-elements, non-editable "islands" or islands with
lakes are the main examples of this issue that I have encountered. The only
somewhat complex element that all browsers can move around cleanly are
inline images. I don't think there is any clear definition of how cursors
should behave in these other cases, but I feel strongly that they should
move around these other elements the same way as images. A slight exception
may be non-editable elements with editable elements inside them inside of
editable elements (island with lake).

Here you can see an example of "converting" footnotes to images so that
copy/paste and cursor movement works:
http://johanneswilm.github.io/canvasContentEditable/ (some issues with
retina displays)


Here you can test moving the caret around the various types of elements. No
browser seems to get it entirely right:
https://bug873883.bugzilla.mozilla.org/attachment.cgi?id=751510


The way others have dealt with it is the inserted of zero-width characters
which then allow for the cursor to be there. That works - except that one
then needs to take care of movemenet across these characters, deletion in
front/behind them, etc. -- altogether quite frustrating.

Check these examples:




>
>
> --
> Robin Berjon - http://berjon.com/ - @robinberjon
>



-- 
Johannes Wilm
Fidus Writer
http://www.fiduswriter.com