Bug 114390 - Enter can't be assigned to insert a manual row break
Summary: Enter can't be assigned to insert a manual row break
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Shortcuts-Accelerators
  Show dependency treegraph
 
Reported: 2017-12-10 19:23 UTC by Sophie Freud
Modified: 2024-06-04 03:14 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sophie Freud 2017-12-10 19:23:08 UTC
Description:
If "insert manual row break" is assigned to Enter in the key customization settings, Enter will still insert a paragraph. This is independent of what is set for Shift+Enter, and out of the two characters, it will always insert a manual row break.

See related LibreOffice Ask post:
https://ask.libreoffice.org/en/question/139847/how-can-i-set-enter-to-insert-a-manual-row-break-not-a-paragraph/

Steps to Reproduce:
1. Assign "insert manual row break" to Enter in the Customization menu
2. Save
3. Press Enter

Actual Results:  
It inserts a paragraph regardless.

Expected Results:
It should respect the new binding and insert a manual row break.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 5.4.3.2 (x64)
Build ID: 92a7159f7e4af62137622921e809f8546db437e5


User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:55.0) Gecko/20100101 Firefox/55.2.2 Waterfox/55.2.2
Comment 1 Dieter 2017-12-12 21:26:49 UTC
I confirm it with

Version: 5.4.2.2 (x64)
Build-ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4
CPU-Threads: 4; Betriebssystem:Windows 6.19; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc: grou
Comment 2 Yousuf Philips (jay) (retired) 2017-12-13 15:26:53 UTC Comment hidden (obsolete)
Comment 3 Sophie Freud 2018-11-16 07:19:19 UTC Comment hidden (no-value)
Comment 4 Dieter 2019-10-15 20:20:38 UTC Comment hidden (obsolete)
Comment 5 digital world 2020-06-02 06:32:03 UTC Comment hidden (spam)
Comment 6 QA Administrators 2022-06-03 03:35:36 UTC Comment hidden (obsolete)
Comment 7 Dieter 2022-06-03 06:16:39 UTC
Still present in

Version: 7.3.4.1 (x64) / LibreOffice Community
Build ID: 13668373362b52f6e3ebcaaecb031bd59a3ac66b
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL
Comment 8 Dieter 2022-06-03 06:18:06 UTC
So I repeat question from Yousuf in comment 2:
Maxim, Muhammet: thoughts?
Comment 9 QA Administrators 2024-06-04 03:14:23 UTC
Dear Sophie Freud,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug