https://bugs.documentfoundation.org/show_bug.cgi?id=103458
Mike Kaganski <mikekagan...@hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #9 from Mike Kaganski <mikekagan...@hotmail.com> ---
IMO, this is not a bug.
1. There is no harm created by the current behavior. Deleting something several
times does not break the document, nor creates anything in the current
redlines.
The alternatives could be:
* on Backspace, stay after the deletion, and eat one character before the
deletion (seemingly what is asked in comment o in "The correct thing"). This is
wrong: the backspace would then eat something not adjacent; you may even have a
situation, when an already deleted part is large, and the place where you
actually delete things is outside of the view.
* on Backspace, jump to before-the-existing-deletion, and delete one character
there. Still not ideal. The first deletion will still be non-adjacent to the
initial cursor position.
* on Backspace, jump to before-the-existing-deletion, and do nothing on this
first keypress. It would be somewhat better - but it would be conceptually no
different compared to the current situation: the first keypress would "delete
the deleted piece again".
Just moving back is something users naturally expect from Backspace; Word does
the same.
Since 2016, there was no duplicates for this; not a single new user CCed to
this (only OP and Ilmari from TDF are there in the list). No sign of a real
user demand.
Let me close it WONTFIX.
--
You are receiving this mail because:
You are the assignee for the bug.
