Michael Ennen

What operating system is this on? I just looked into the implementation of closeCurrentWindow, [here](https://github.com/TestFX/TestFX/blob/216324d73c259f3fa2eaac6a7a23a28325481fbe/subprojects/testfx-core/src/main/java/org/testfx/api/FxRobot.java#L562). Manually pressing alt-f4 seems like a hack and I wonder if it is system dependent.

Can you try to grab the window/stage using FxRobot.listWindows(), FxRobot.listTargetWindows(), or any of the FxRobot.window(..) methods? Then request close on that?

Hmm what does the following do if you add it to your test: `stage.getOwner().setOnHidden(() -> System.out.println("Window has been hidden!");` Also can you check what `stage.getOwner().isShowing()` returns after you expect it...

`getOwner()` will only work if you use `initOwner(owner)` before making the `Dialog` (in this case, `Alert`) visible. I am not sure if it will make a difference in this case,...

I thought that you are using `closeCurrentWindow()` not calling `close()` directly on the Alert?

Even it is a long shot to somehow get a handle to the alert stage (can you call `setId()` on it and access via `lookup(#id)`?) try and get one and...

This is not intentional - something must be wrong with our GroovyDoc generation. The source can be found here: https://github.com/TestFX/TestFX/tree/master/subprojects/testfx-spock I attempted to generate the GroovyDoc thusly: https://github.com/TestFX/TestFX/blob/master/subprojects/testfx-spock/testfx-spock.gradle#L42 https://github.com/TestFX/TestFX/blob/master/subprojects/testfx-spock/testfx-spock.gradle#L67

`MenuItem` assertJ assertions have not been added yet. See https://github.com/TestFX/TestFX/pull/584#issuecomment-399269603 for a description of what is needed.

Exceptions like that happen when JavaFX encounters a buffer overflow, they are very difficult to debug in my experience. Is this happening in headed or headless mode? Of course, it...

Would you be open to submitting a pull request?