GnuCash
Contact   Instructions
Bug 797839 - Auto-complete prevents entering non-ASCII transaction descriptions
Summary: Auto-complete prevents entering non-ASCII transaction descriptions
Status: RESOLVED FIXED
Alias: None
Product: GnuCash
Classification: Unclassified
Component: User Interface General (show other bugs)
Version: 4.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: ui
QA Contact: ui
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-02 17:20 EDT by Mihail Balabanov
Modified: 2020-09-07 14:45 EDT (History)
7 users (show)

See Also:


Attachments
A file with transaction descriptions in Cyrillic, can be used for repro steps. (4.39 KB, application/x-gnucash)
2020-07-02 17:20 EDT, Mihail Balabanov
no flags Details

Description Mihail Balabanov 2020-07-02 17:20:19 EDT
Created attachment 373765 [details]
A file with transaction descriptions in Cyrillic, can be used for repro steps.

Steps to reproduce if you have any Cyrillic keyboard layout installed
---------------------------------------------------------------------
1. Load the attached file.
2. Open 'Expenses' or 'Checking account'. There should be 30 entries, one for each letter of the Bulgarian alphabet.
3. Type (not paste) any Cyrillic letter in the description field of a new transaction, for example 'Г'.

Actual results
--------------
Autocomplete will fill in a suggestion ('Грозде'), put the cursor at the start of the entry, and select the entire entry.
If you now type another letter, say 'И', 'Грозде' will be replaced with 'Извара'.
If you continue typing letters matching the existing entries, autocomplete will just cycle through suggestions, preventing you from entering any text.

Expected results
----------------
After filling in a suggestion, autocomplete should put the cursor after the characters entered by the user and select only the characters after the cursor.
Continuing the example, if you type 'И' as a second letter, the description field should read 'ГИ'.

Note
----
I tried several other non-ASCII characters and also managed to trigger the issue so if you don't have a Cyrillic layout, you may be able to reproduce the issue with any other non-ASCII entries.

(This is different from issue 796734 where the autocompleted characters are not selected at all.)
Comment 1 voldermort 2020-07-06 09:29:01 EDT
Same with Hebrew.
Comment 2 Alexey Kosilin 2020-07-10 02:46:36 EDT
I see exactly the same behaviuor under Fedora 32 Linux using UTF-8 Cyrillic codeset at least. While I'm trying to type using ASCII (1-byte) letters everything seems to be ok.
Comment 3 John Ralls 2020-07-10 18:51:46 EDT
Fixed for 4.1. Thanks for reporting it.
Comment 4 voldermort 2020-08-03 05:12:46 EDT
Still broken in 4.1 (Windows) for Hebrew. May be relevant that Hebrew is RTL.
Comment 5 John Ralls 2020-08-03 16:19:24 EDT
I think I found it. Please test with tomorrow's nightly from https://code.gnucash.org/builds/win32/maint.
Comment 6 Alexey Kosilin 2020-08-03 17:56:18 EDT
(In reply to John Ralls from comment #3)
> Fixed for 4.1. Thanks for reporting it.

Thank you for good job! The bug is definitely fixed in 4.1 at least for usual "left-to-right" languages.

Alexey.
Comment 7 John Ralls 2020-09-07 14:45:01 EDT
Closing as fixed, voldermort having not responded in a month.

Note You need to log in before you can comment on or make changes to this bug.