Re: CTRL+BACKSPACE or its equivalent behavior when deleting block elements

Hey,
this sounds like a contenteditable=true issue. We originally moved on to
work on other parts because the number of issues and inconsistencies of
cE=true were so numerous that it did not seem solvable in the next decade.

But now it sounds as if there is some interest in trying to standardize it.
Is that correct?

On Thu, Feb 11, 2016 at 12:01 PM, Chaals McCathie Nevile <
chaals@yandex-team.ru> wrote:

> Hi,
>
> On Thu, 11 Feb 2016 03:38:33 +0100, Grisha Lyukshin <glyuk@microsoft.com>
> wrote:
>
> Hello All,
>>
>> There is a special behavior that is currently not interoperable between
>> browsers for a specific use case below:
>>
>> I think we should only delete one block element at a time when
>> CTRL+BACKSPACE is pressed.
>>
>> Chrome, FF and Edge all behave differently (sorry, I don't have Mac to
>> test how Safari behaves).
>>
>> Repro steps:
>>
>> jsfiddle<https://jsfiddle.net/svn9Lztd/>
>>
>> Place the caret in front of "def" and press CTRL+BACKSPACE
>>
>
> Opening this in Yandex.browser (blink-based), Safari and Firefox on mac,
> and pressing command-backspace, Firefox deleted everything in 4 steps, the
> other two in 5. (ctrl-backspace did nothing in FF and a normal backspace in
> the other two).
>
> It seems Firefox deletes the paragraph when it removes the last thing in
> it, whereas the others remove the text node in a separate operation. What
> happened on windows? (I don't have a windows machine here to test…)
>
> Cheers
>
> Chaals
>
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
>  chaals@yandex-team.ru - - - Find more at http://yandex.com
>
>


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