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 tree / graph
 
Reported: 2022-03-14 12:34 UTC by sdc.blanco
Modified: 2022-03-15 12:43 UTC (History)
0 users

See Also:
Crash report or crash signature:
Regression By:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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+