https://bugs.documentfoundation.org/show_bug.cgi?id=119065
Heiko Tietze <tietze.heiko@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #8 from Heiko Tietze <tietze.heiko@gmail.com> ---
The problem is that it behaves differently not only to the previous versions
but also to current Writer.
(In reply to Mark Hung from comment #7)
* Press "Del" at the end of the line: connect next paragraph to the current
paragraph, and the paragraph style ( including bullet status ) for the
current paragraph remains.
* Press "Backspace" at the beginning of the line: connect the current
paragraph to the previous paragraph, and make the previous paragraph have
the same style ( including bullet status ) as the current one.
True, but the question is what happens when you backspace at the end of the
line. There is no reason to delete the bullet
My patch there uncovered the delicate design of the original designer (from
ooo age). I've once wanted to document the difference. It works as expected
buy maybe we need UX eval here.
No, the expectation is to delete the bullet with backspace at the beginning of
the line but not the end.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 119065] Formatting: Last bullet of the bullet list is disappearing after removing a item from the bulleted list using backspace · bugzilla-daemon
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.