Bug 424990 - Tab key changes focus from field with Automatic and Short Automatic completion rather than completing current path
Summary: Tab key changes focus from field with Automatic and Short Automatic completio...
Status: REPORTED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: URL navigator (show other bugs)
Version: 5.72.0
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-04 06:47 UTC by Thomas Carmichael
Modified: 2020-08-26 19:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Carmichael 2020-08-04 06:47:02 UTC
SUMMARY
The Tab key behaviour with the Automatic and Short Automatic completion options does not work as expected, moving the focus from the editable location bar, rather than completing the path.

STEPS TO REPRODUCE
1. Start typing an existing path and be presented with the with some faded completion text, e.g. using '/usr/share/plasma/plasmoids/org' will present either the first sub-directory ('org.kde.desktopcontainment' for me) for Automatic completion or the shortened common path ('org.kde.') for Short Automatic completion.
2. Press the Tab key to accept the completion.

OBSERVED RESULT
Pressing the Tab key completes the path entry as per the completion, but moves the focus from the location bar.

EXPECTED RESULT
Pressing the Tab key completes the path entry as per the completion and the focus stays in the location bar. A subsequent press of the Tab key would then move the focus out of the location bar.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 5.19
KDE Plasma Version: 5.19.3
KDE Frameworks Version: 5.72.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
It is still possible to use the End key here, but this requires more movement away from the home row when typing than using the Tab key does. My expectation for what happens here comes from a combination of familiarity with shell-style completion and previous use of Nautilus for some of the path editing behaviour (the behaviour is consistent in other GTK based file managers as well).
Comment 1 Nate Graham 2020-08-10 18:10:31 UTC
How is this different from Bug 424991?
Comment 2 Thomas Carmichael 2020-08-11 05:00:05 UTC
This differs from Bug 424991 in that it's related to the Tab key behaviour as it relates to the Automatic/Short Automatic completion and after looking at the issue reporting page (https://community.kde.org/Get_Involved/Issue_Reporting#One_issue_per_Bugzilla_ticket) I realised that the issues seemed different enough that they should be separated.
Comment 3 Nate Graham 2020-08-11 05:04:46 UTC
I think my question is the same for both, though: if the tab key is changed to trigger autocompletion rather than moving the keyboard focus, then how would do you move the keyboard focus using the keyboard?
Comment 4 Thomas Carmichael 2020-08-11 05:16:03 UTC
I left a comment on Bug 424991 since I think there would be more usability issues for that one.

For this one however, I would expect that the idea of a second press of the Tab key would complete the faded completion text and then in the absence of additional completion, the focus should move out of the field.

Using the Steps to Reproduce example path, this would mean that using '/usr/share/plasma/plasmoids/org' for Automatic completion, the path would become '/usr/share/plasma/plasmoids/org.kde.desktopcontainment' and pressing Tab after that would move the focus. For Short Automatic completion I'd expect the path to be '/usr/share/plasma/plasmoids/org.kde.' and then pressing Tab would again, move the focus.
Comment 5 Bug Janitor Service 2020-08-26 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Christoph Feck 2020-08-26 19:19:42 UTC
New information was added with comment 4; changing status for inspection.