Bug 142034 - Selecting (single left-click) cell enters edit mode directly when compose character on keyboard was struck beforehand
Summary: Selecting (single left-click) cell enters edit mode directly when compose cha...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.1.2.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-01 23:15 UTC by Andrew Siplas
Modified: 2022-11-24 03:42 UTC (History)
1 user (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 Andrew Siplas 2021-05-01 23:15:03 UTC
Description:
Calc, when the compose key (https://en.wikipedia.org/wiki/Compose_key) has been pressed, will directly start editing a cell on single-click.

Reproduce:



It's not clear this is desired behavior—this occurs even long periods after compose key has been struck but not used.

Steps to Reproduce:
1. Press «compose» key on keyboard (or bind to an alternate key and use that), but don't press any further key—leave OS waiting for 2nd/3rd keystroke to compose the character.
2. Single-click any cell in calc from an idle (but not read-only) state.

Actual Results:
Calc enters edit mode right away, navigating away by further click on another cell results in cell contents cleared.

Expected Results:
Editing a cell would require a double click, clicking outside the cell would *NOT* clear the contents—pending character from before-the-fact should not clear cell contents not explicitly edited by user.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Held the compose event until getting a further keystroke, e.g. if compose character is pending, wait for the '/' and 'c' keystrikes to make the ¢ (cent) mark, for example, and don't enter edit until complete character is received.

At least don't interpret a keystrike from 10 minutes earlier as input upon clicking a cell.
Comment 1 Buovjaga 2022-04-26 11:10:51 UTC
To make sure I got the key right, I customised it like in the instructions here:
https://userbase.kde.org/Tutorials/ComposeKey

I could not reproduce your problem.

After testing with kf5, gtk3 and x11 UI backends, I noticed that only gtk3 showed an effect when I pressed the compose key. It went into edit mode in the focused cell and showed some indicator, underline and dot.

Please copy and paste here the contents of your Help - About. This allows us to know more about your system. Separately, mention the Linux distribution you are using. Please also test again with 7.3.

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the information.

Arch Linux 64-bit
Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: 37613bffe4621c444e5a34678bafb2c3a875263d
CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded Jumbo
Built on 26 April 2022
Comment 2 QA Administrators 2022-10-24 03:42:36 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2022-11-24 03:42:26 UTC
Dear Andrew Siplas,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp