Bug 474923 - .desktop properties dialog has incorrect tab order
Summary: .desktop properties dialog has incorrect tab order
Status: RESOLVED DUPLICATE of bug 460647
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: Properties dialog (show other bugs)
Version: 5.110.0
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-26 22:43 UTC by JT Hundley
Modified: 2023-09-28 19:38 UTC (History)
5 users (show)

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

Attachments
Illustrated tab order of the dialog (72.19 KB, image/png)
2023-09-26 22:43 UTC, JT Hundley 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description JT Hundley 2023-09-26 22:43:45 UTC 
Created attachment 161893 [details]
Illustrated tab order of the dialog

The tab order of the Application tab within the .desktop properties dialog has the incorrect tab order


STEPS TO REPRODUCE
1. Find any .desktop file
2. Right click on it, select properties
3. Select the Application tab at the top
4. Press tab multiple times and observe which fields receive focus

OBSERVED RESULT
The tab order is top to bottom except it skips over the Arguments field. Instead it goes from the Program Browse button to the Work path field, then the ork path button, and then finally Arguments.

EXPECTED RESULT
Pressing tab should bring focus from the Browse button to the Arguments field and then to the Work path field.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Comment 1 Patrick Silva 2023-09-27 13:18:59 UTC 
Can reproduce on my Arch Linux too.
Comment 2 Nicolas Fella 2023-09-27 13:25:44 UTC 
duplicate of https://bugs.kde.org/show_bug.cgi?id=460647 ?
Comment 3 JT Hundley 2023-09-28 00:31:25 UTC 
(In reply to Nicolas Fella from comment #2)
> duplicate of https://bugs.kde.org/show_bug.cgi?id=460647 ?

You are correct, it is a duplicate. I swear I searched first! :)
Comment 4 Nate Graham 2023-09-28 19:38:02 UTC 
Yup.

*** This bug has been marked as a duplicate of bug 460647 ***