Bug 468254 - AUT Activation by Tabbing
Summary: AUT Activation by Tabbing
Status: NEW
Alias: None
Product: Jubula (Archived)
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2015-05-26 02:23 EDT by Dominik Gabriel CLA
Modified: 2015-05-28 03:57 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dominik Gabriel CLA 2015-05-26 02:23:17 EDT
I know there was another Issue before and there is a workaround to handle the AUT Activation by tabbing but it would be really nice to give the user the possibility to set tabbing as default for the AUT Activation in the AUT configuration. 
Its an old problem that the click version isn't always working because there could be another windows that is covering your AUT. It would be really nice when a program like Jubula could handle that by itself and doesn't need any workaround for that.
Comment 1 Alexandra Schladebeck CLA 2015-05-28 03:57:43 EDT
Thanks for putting this in Dominik. We have talked about an action that could bring an AUT to the foreground, and I agree it would be a lovely action to have. The reason we've not done it yet is that bringing windows to the foreground is highly platform and toolkit specific. It's not (according to our estimations) something that is quickly done. 

That's the reason as well why we're not likely to work on it in the near future. I've added the helpwanted tag to this ticket because we'd love to have input from the community on this. 

For the moment, the workaround is to:
- Click in the active window
- React to an "action error" (for if the window is not the correct one) with a retry event handler by pressing alt+shift+tab