Bug 147986 - Position in shortcut keys should not change after using Reset button in Customize Keyboard
Summary: Position in shortcut keys should not change after using Reset button in Custo...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.2.5.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Customize-Dialog-Keyboard
  Show dependency treegraph
 
Reported: 2022-03-14 12:34 UTC by sdc.blanco
Modified: 2024-03-15 03:15 UTC (History)
0 users

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 sdc.blanco 2022-03-14 12:34:01 UTC
Steps to illustrate situation:
1. Tools>Customize>Keyboard tab
2. Scroll down in Shortcut Keys window and select an empty key combination (e.g., Shift+F15)
3. Choose any Function and assign to the empty key combination by clicking on Modify.
4. Click on Reset (on the right side of the window)

Actual: Shortcut key window returns to the top of the window.
Expected:  Position remains unchanged
Comment 1 LeroyG 2022-03-14 22:23:17 UTC
Works as expected in:
Version: 7.1.8.1 (x64) / LibreOffice Community
Build ID: e1f30c802c3269a1d052614453f260e49458c82c
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: es-MX (es_ES); UI: es-ES
Calc: CL
Comment 2 Shinji Enoki 2022-03-15 11:58:01 UTC
This case reset worked correctly, but the pointer position in the list moved up. I think this report is a usability issue

Reproduced in:

Version: 7.3.1.3 / LibreOffice Community
Build ID: a69ca51ded25f3eefd52d7bf9a5fad8c90b87951
CPU threads: 8; OS: Linux 5.16; UI render: default; VCL: gtk3
Locale: ja-JP (ja_JP.UTF-8); UI: ja-JP
Calc: threaded
Comment 3 sdc.blanco 2022-03-15 12:43:21 UTC
(In reply to Shinji Enoki from comment #2)
> I think this report is a usability issue
Correct. The issue is usability.

Also reproduced in 7.4.0.0+
Comment 4 QA Administrators 2024-03-15 03:15:19 UTC
Dear sdc.blanco,

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