On Thu, 11 Jan 2024 23:54:13 GMT, Kevin Rushforth wrote:
>> As described in the JBS bug, there is a long-standing deadlock that happens
>> on macOS between the AWT EDT and the JavaFX Application thread (which on
>> macOS is the AppKit thread) when processing Input Method Events (IME) in a
>> W
On Thu, 11 Jan 2024 23:54:13 GMT, Kevin Rushforth wrote:
>> As described in the JBS bug, there is a long-standing deadlock that happens
>> on macOS between the AWT EDT and the JavaFX Application thread (which on
>> macOS is the AppKit thread) when processing Input Method Events (IME) in a
>> W
On Thu, 11 Jan 2024 23:54:13 GMT, Kevin Rushforth wrote:
>> As described in the JBS bug, there is a long-standing deadlock that happens
>> on macOS between the AWT EDT and the JavaFX Application thread (which on
>> macOS is the AppKit thread) when processing Input Method Events (IME) in a
>> W
> As described in the JBS bug, there is a long-standing deadlock that happens
> on macOS between the AWT EDT and the JavaFX Application thread (which on
> macOS is the AppKit thread) when processing Input Method Events (IME) in a
> WebView node in a JFXPanel.
>
> This PR fixes the deadlock by a
On Wed, 10 Jan 2024 14:54:47 GMT, Kevin Rushforth wrote:
> As described in the JBS bug, there is a long-standing deadlock that happens
> on macOS between the AWT EDT and the JavaFX Application thread (which on
> macOS is the AppKit thread) when processing Input Method Events (IME) in a
> WebVi
On Wed, 10 Jan 2024 14:54:47 GMT, Kevin Rushforth wrote:
> As described in the JBS bug, there is a long-standing deadlock that happens
> on macOS between the AWT EDT and the JavaFX Application thread (which on
> macOS is the AppKit thread) when processing Input Method Events (IME) in a
> WebVi