Bug Hunting Session
Bug 49091 - UI: Alt-Left, Alt-Right keyboard shortcuts ineffective
Summary: UI: Alt-Left, Alt-Right keyboard shortcuts ineffective
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsDevEval, topicDebug, topicUI
: 53190 93402 (view as bug list)
Depends on:
Blocks: Shortcuts-Accelerators
  Show dependency treegraph
 
Reported: 2012-04-23 15:43 UTC by ryan.jendoubi@gmail.com
Modified: 2017-06-16 10:49 UTC (History)
8 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 ryan.jendoubi@gmail.com 2012-04-23 15:43:13 UTC
Just spent 20 minutes getting very confused as to why I couldn't assign the Navigation controls "Back" and "Forward" to a keyboard shortcut. Had a nice long bug report all typed up for it, but before posting tried different shortcuts...

Sure enough, I could assign them to Alt-B and Alt-F, but not Alt-Left and Alt-Right :p

A little more experimenting and it seems that no matter what one assigns to these combinations, all that happens is the cursor moves left and right completely normally: their shortcut function isn't activated at all.

I haven't upgraded to the 5.x series yet for a number of reasons (including Bug 47764 and Bug 46155) so I'd appreciate if someone else could check that this bug still exists in the newest versions :-)

Steps to reproduce: In LibreOffice Writer:
1. Go to the Tools menu > Customize...
2. If not selected, select the Keyboard tab
3. Assign some (any) function to the Alt-Left and Alt-Right key combinations
4. Return to your document
5. Test the Alt-Left and Alt-Right keyboard shortcuts
*Result: No effect: shortcut functions not activated*
Comment 1 Rainer Bielefeld Retired 2012-04-24 01:52:35 UTC
[Reproducible] with "LibreOffice 3.5.3.1 (RC1) German UI/Locale [Build-ID: 21cb047-d7e6025-9ba54fc-b4a51a8-f42372b] on German WIN7 Home Premium (64bit). I tried to associate a  macro to <Alt+leftarrow>, failed. macro is shown in list of shortcuts, but it will not be executed.

It's different in Calc, there <Alt+leftarrow> and <Alt+rightarrow> are used, but I can customize, I tried to associate a macro to <Alt+leftarrow>, worked fine.
Comment 2 Joel Madero 2014-02-27 23:28:30 UTC
In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval.

Thank you and apologies for the noise
Comment 3 Rachit Gupta 2014-04-10 04:54:17 UTC
I'm working on this bug. Seems like Alt+<any_arrow_key> does not work.
Comment 4 Regina Henschel 2014-04-14 17:39:14 UTC
It depends on the context.
If a graphic object or a presentation object is selected, then Alt+Arrow is used for one pixel movement of the object or in point mode for movement of a single point.
If the cursor is inside a Writer table, Alt+LeftArrow and Alt+RightArrow is used to manipulate the column width, Alt+UpArrow and Alt+DownArrow for row height. In addition there are some bindings for languages with composed character.
In accessibility context Alt+DownArrow and Alt+UpArrow is used to open/close a drop-down-list in a dialog or a combox-box in forms.
In Calc Alt+DownArrow and Alt+UpArrow depends on the chosen key bindings in Tools>Options>Calc>Compatibility.

So it is not true that "Alt+<any_arrow_key> does not work". So when you alter something please make sure, that the existing bindings still work.
Comment 5 Rachit Gupta 2014-04-15 15:08:04 UTC
Actually what I meant was that when we assign a new binding to Alt+<any_arrow_key>, the assigned bindings do not work. So more than 1 bindings can be assigned to Alt+<any_arrow_key> ? And when the key combination is pressed, then all the actions are to be performed?
Comment 6 Rachit Gupta 2014-04-18 05:34:45 UTC
Or, maybe if Alt+<arrow_keys> already have predefined assignments, maybe we could remove these key bindings from being customized by the user?
Comment 7 Kohei Yoshida 2014-04-23 13:16:39 UTC
Just FYI, the expected action is that, if a user assigns a custom action, that one should take precedence.  If no action is mapped, whatever writer does by default should be triggered.  Calc does it that way too.  I'm surprised Writer didn't follow this behavior.
Comment 8 Kohei Yoshida 2014-04-23 13:24:29 UTC
But I do see some element of complexity in handling this, as Regina outlined in Comment 4.
Comment 9 Rachit Gupta 2014-04-25 10:49:23 UTC
Hello,

I won't be able to work on this bug any more. Someone else can take it. I'll share some of my findings:

The code for the key combinations in Writer is held in sw/source/core/uibase/docvw/edtwin.cxx, search for the while loop in the KeyInput method. The variable eKeyState does not get set to KS_KeyToView, which results in the key combinations being ineffective.

Regards,
Rachit Gupta
Comment 10 V Stuart Foote 2015-08-17 01:28:39 UTC
*** Bug 93402 has been marked as a duplicate of this bug. ***
Comment 11 tommy27 2015-10-17 08:39:53 UTC
just to tell that OOo 3.3.0 had the same problem with those "Alt+Left" and "Alt-Right" keyboard shortcuts

problem persists in LibO 5.1.0.0 alpha too
Comment 12 Robinson Tryon (qubit) 2015-12-13 10:25:39 UTC Comment hidden (obsolete)
Comment 13 Björn Michaelsen 2016-01-26 18:02:37 UTC
topicDebug is a Topic.
Comment 14 Björn Michaelsen 2016-01-26 18:04:57 UTC
Remove skillDebug, superceded by topicDebug.
Comment 15 Buovjaga 2016-03-09 08:35:28 UTC
*** Bug 53190 has been marked as a duplicate of this bug. ***
Comment 16 Björn Michaelsen 2016-03-29 22:58:16 UTC
55838 and 49091 are possibly related
Comment 17 QA Administrators 2017-05-22 13:20:29 UTC
** Please read this message in its entirety before responding **

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 on a currently supported version of LibreOffice 
(5.2.7 or 5.3.3  https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and 
your operating system, and any changes you see in the bug behavior
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave 
a short comment that includes your version of LibreOffice and Operating System

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)

http://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: http://webchat.freenode.net/?channels=libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug-20170522