Bug 123177 - Key combination not properly processed
Summary: Key combination not properly processed
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Shortcuts-Accelerators
  Show dependency treegraph
 
Reported: 2019-02-05 10:58 UTC by Heiko Tietze
Modified: 2022-08-01 03:26 UTC (History)
4 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 Heiko Tietze 2019-02-05 10:58:04 UTC
The patch [1] for bug 121596 uses Shift+Alt+Space to insert a special character (U+202F / E280AF). It works perfectly on Linux but on macOS a different value (U+A0 / C2A0 / No-Break space) is inserted. Pressing this key combination bypasses the SwEditWin::KeyInput() function (debugger breakpoint not hit).

There might be other key combinations that also not work.

[1] https://gerrit.libreoffice.org/#/c/66776/
Comment 1 Alex Thurgood 2019-02-06 09:33:31 UTC
Confirming in

Version: 6.3.0.0.alpha0+
Build ID: e9db8eceff48290be72591f7422b4fc45e5752fc
CPU threads: 4; OS: Mac OS X 10.14.2; UI render: default; VCL: osx; 
Locale: fr-FR (fr_FR.UTF-8); UI-Language: en-US
Calc: threaded


Both Alt+Space and Shift+Alt+Space appear to insert the same type of space, at least in Writer (haven't tested the other modules).
Comment 2 Heiko Tietze 2019-02-06 15:09:18 UTC
(In reply to Alex Thurgood from comment #1)
> Confirming...

Alex, could you please test other key combinations to see if the issue is restricted to exactly shift+mod2+space or shift+mod2 or mod2+space etc. Gut feeling is that mod2 is taken as mod1 somehow.
Comment 3 QA Administrators 2022-08-01 03:26:46 UTC
Dear Heiko Tietze,

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