Re: [w3c/editing] RFC: Contenteditable "indent"/"outdent" implementations are not aligned with popular editors (Issue #437)

Hey, could you make separate issues for each of those points?

@simon What will thr research exactly entail? Will you check whether
changing the browser engine will break popular JavaScript editors? That
would be the main problem if any of this code is changed.

On Thu, Sep 21, 2023, 13:21 joanmarie ***@***.***> wrote:

> (Another thing for Simon's research that falls under this umbrella)
>
> In popular editors, if you indent something and then immediately outdent
> it, the result is as if you made no changes. IMHO, that is the expected
> result, both for the popular editors and for native contenteditable
> elements.
>
> If you try anything but the simplest of cases, especially in Chromium and
> WebKit, the result is ... Well, try it out yourself. 😀 You can make it
> more visually obvious by using multiple levels of divs with colored
> borders and some brs sprinkled throughout.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/editing/issues/437#issuecomment-1729370252>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAERMOD462BMI3AOO2GX7TLX3QPNNANCNFSM6AAAAAA4HOREMU>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/437#issuecomment-1729441975
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/editing/issues/437/1729441975@github.com>