https://bugs.documentfoundation.org/show_bug.cgi?id=71501
Heiko Tietze <heiko.tietze@documentfoundation.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cno@nouenoff.nl,
| |mikekaganski@hotmail.com,
| |nemeth@numbertext.org
--- Comment #15 from Heiko Tietze <heiko.tietze@documentfoundation.org> ---
Ctrl+enter is placed before the table but becomes not active until a first
character is inserted via at+enter.
The documentation part should have been solved with bug 112804. Bug 105333 and
84806 discuss the same/similar topic, and was solve recently by Lazlo.
Harald created also the duplicate bug 71503, one is the generic issue and the
other his expectation (enter at the very first item at the table behaves
special). And this is actually a question to me. Once enter at position 0 of
the table adds a paragraph above, the workaround to insert a break at position
0 could be to insert a space first. Sounds reasonable simple to me, rather to
point users to the documentation and to learn alt+enter. And it sounds much
better than the proposed solution in bug 51689.
We should investigate how alt+enter is implemented (likely hard-coded) and free
this shortcut for customization.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 71501] EDITING: “Enter“ in first Cell of Table Creates a Paragraph above Table · 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.