*muttering to myself ..
Meanwhile, my understanding evolved a bit - there are actually two
refiring scenarios, both wrecking the event dispatch sequence, the
first more evil than the second
1. getParent.fireEvent(receivedKeyEvent) which leads to serious
misbehaviour (as reported f.i.
While fixing https://bugs.openjdk.java.net/browse/JDK-8207759 it
turned out that the underlying reason for the bug was a broken event
dispatch sequence introduced by behavior.forwardToParent. Which is a
call to parent.fireEvent with the event that was received. This builds
a nested
