Bug 477325 - JavaFX Toolkit - press key combination - ActionError (Timeout) when other action is being activated by pressing key before it is released
Summary: JavaFX Toolkit - press key combination - ActionError (Timeout) when other act...
Status: CLOSED WORKSFORME
Alias: None
Product: Jubula (Archived)
Classification: Technology
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: All Windows NT
: P3 enhancement (vote)
Target Milestone: 4.0   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 421595
  Show dependency tree
 
Reported: 2015-09-14 03:49 EDT by Maissmaallsmyss Maulhs-Vvuillss CLA
Modified: 2016-05-19 03:38 EDT (History)
3 users (show)

See Also:


Attachments
Test Results (3.20 KB, application/empty)
2015-09-14 03:49 EDT, Maissmaallsmyss Maulhs-Vvuillss CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Maissmaallsmyss Maulhs-Vvuillss CLA 2015-09-14 03:49:24 EDT
Created attachment 256544 [details]
Test Results

In some cases I get an action error (Timeout) by unsing press any key action (unbound modules) when this action activates opening of a dialog, what prevents the action to be completed (relase is not exetuced). So I cannot close the dialog becouse I get the action error before I get to the test step to close the dialog. 
I can avoid this situation by using external key combinations. But as discussed with Markus Tiede, this issue may still be worth investigation.

As far as I have understood, in the java FX application in my project in some cases we prevent the press key action to be relased before we get the answer from the user if this action should be exectuted or canseled. That´s why I got errors by using normal key combinations (not the external ones). 

Jubula 8.1.7

There is no relevant information in the client logs.

Java FX log:
2015-09-14 08:57:11.251 [Connection.ReaderThread:Socket[addr=/10.54.255.17,port=56192,localport=56214]] WARN  o.e.j.r.j.d.KeyJavaFXEventMatcher - Key event matching fallback used.

Test results are attached.
Comment 1 Maissmaallsmyss Maulhs-Vvuillss CLA 2015-09-14 03:52:04 EDT
By any technical questions regarding this issue Kristian Wolpers will be able to help.
Comment 2 Alexandra Schladebeck CLA 2016-05-11 09:58:32 EDT
After speaking to Kristian, this is probably still the case. 

His assumption is that our event confirmation doesn't work, because the AUT already catches an event on the key down. Jubula waits for the key-up event, which then doesn't come. 

Since using external key combination seems to work, closing as worksforme until any other information is added.
Comment 3 Oliver Goetz CLA 2016-05-13 02:42:57 EDT
Closed due to comment 2