Hi Paul,
I think this is a good solution to the problem. As you pointed out, this
needs a CSR to capture the behavioral change that receiving the openURI
even on macOS will cause JavaFX to start the AWT toolkit if it isn't
already started.
I don't have any overall concerns. Let's proceed with the PR and
continue discussing the details there.
-- Kevin
On 9/28/2026 2:28 AM, Paul wrote:
Hello,
I would like to discuss a change for fixing the issue described inside this PR:
https://github.com/openjdk/jfx/pull/2203.
The problem in short terms is that when Your application is installed with like
jpackage and registered to receive URI events on MacOS and You open it with an
URI (like in the terminal with ‘open myapp://hello-world') it won’t receive the
first URI if it is not already running. This is due to the fact that JavaFX is
initialized first and forwards the event to AWT, but AWT is not yet initialized
and therefore can’t handle the event correctly.
The proposed fix would require JavaFX to initialize AWT first, before sending
the event. This of course means some change in the behavior of JavaFX which
might be unexpected and could potentially cause some issues. That’s why I
wanted to discuss this change to make sure everything works as expected and
that this approach is a feasible solution for the problem.
There is also a CSR already created for this issue:
https://bugs.openjdk.org/browse/JDK-8391252.
Best Regards
Paul
