Bug 361591 - Tab order in new custom document dialogue switches from width to resolution instead of hight
Summary: Tab order in new custom document dialogue switches from width to resolution i...
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Usability (show other bugs)
Version: 3.0 Alpha
Platform: Mint (Ubuntu based) Linux
: NOR minor
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-10 11:17 UTC by Amir Adar
Modified: 2016-04-10 15:18 UTC (History)
1 user (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 Amir Adar 2016-04-10 11:17:00 UTC
When creating a new custom document, and trying to navigate the different fields using tab, the tab order skips the "Height" field after modifying the "Width" field, straight to the "Resolution" field. The "Height" field only gets selected after pressing tab again.

Reproducible: Always

Steps to Reproduce:
1. Open the new document dialogue and choose custom document.
2. Select the "Width" field.
3. Press tab.

Actual Results:  
The next selected field is "Resolution".

Expected Results:  
The next selected field should be "Height". "Height" is only selected after pressing tab again.
Comment 1 wolthera 2016-04-10 12:40:29 UTC
I cannot confirm this on Ubuntu 15.10, might have been fixed in the past week because the code for the alpha is based on that for monday. Thanks for the report regardless, if you find any other bugs, we're welcoming them :)
Comment 2 Amir Adar 2016-04-10 15:01:05 UTC
Thank you for the reply. :)
I didn't realize this was an old build. I downloaded it yesterday from the pre-alpha 3 announcement post (https://krita.org/item/3-0-pre-alpha-3-is-out/), so I figured it must have been the latest. Now I see there's another build in the download page. Should I use the one from there if I want to keep testing?
Comment 3 wolthera 2016-04-10 15:11:39 UTC
Oh, no don't worry about. If I am right we used an old version of the source deliberately because of organisational reasons(like, the code used in the release is the same as in the tarballs for the alpha, which makes it the same code, and thus clearer). Just continue resting with the build you have.

The new alpha packages are mostly there to fix an issue with fedora.
Comment 4 Amir Adar 2016-04-10 15:18:16 UTC
Very well. Thanks again! :)