Bug 143835 - [UI]/[EDITING] Formula bar only accepts dead key inputs when typing in it for the first time
Summary: [UI]/[EDITING] Formula bar only accepts dead key inputs when typing in it for...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.1.0.3 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-12 10:00 UTC by gujochino
Modified: 2023-12-04 03:18 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 gujochino 2021-08-12 10:00:00 UTC
Description:
As a multilingual user, I rely heavily on dead key inputs but since at least a few months (before 7.1.0.3 and still true as of 7.1.5.2), I can only type dead key combinations when clicking on the formula bar for the first time. If I select a new cell and type complex combinations, everything works fine. If I then move to another cell and back, I can only do get the combinations to work if I completely replace the content of the cell, not if I try typing from the formula bar. Strangely, I can still type the combination I want in the Font size or Font name fields for instance and currently typically write the full accented sentences there before copy and pasting back into the main field. Writer works fine with dead keys and I don't get any message when launching calc from the terminal.

Steps to Reproduce:
1. Select any cell and type anything then move to another cell
2. Select the first cell and click on the formula bar
3. Try typing anything with a valid dead key combination on the tester's active layout (for instance SUPER+u+u, '+e, CTRL+SHIFT+u+2+0+0…)

Actual Results:
The dead key input is completely ignored, yielding uu, e and 200 in the three examples specified above

Expected Results:
The dead key input is taken into account, yielding ŭ, é and Ȁ in the examples above


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Version: 7.1.5.2 / LibreOffice Community
Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-US (en_IE.UTF-8); UI: en-US
Calc: threaded
Comment 1 Stéphane Guillou (stragu) 2023-05-06 00:25:17 UTC
I can't reproduce the issue in:

Version: 7.1.0.3 / LibreOffice Community
Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Nor in:

Version: 7.5.3.2 (X86_64) / LibreOffice Community
Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

I tested with accent dead keys (accute, umlaut, tilde...) on a German keyboard layout.

Can you please test again with currently supported versions (7.4 or 7.5) and let us know if you can still reproduce?
If so, which keyboard layout are you using?
Comment 2 QA Administrators 2023-11-03 03:15:33 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2023-12-04 03:18:08 UTC
Dear gujochino,

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