Hi Mike,
thank you for your pointers!
On 14.05.2020 14:21, Mike Hearn wrote:
> The WebKit binding code is some of the more complex code in JavaFX. Rather
> than try to extend the
> script tag you could instead look at the code for the tag and the
> old support for
> Netscape-style plugins.
>
The WebKit binding code is some of the more complex code in JavaFX. Rather
than try to extend the script tag you could instead look at the code for
the tag and the old support for Netscape-style plugins.
On 09.05.2020 17:23, Kevin Rushforth wrote:
> WebEngine uses WebKit's JavaScriptCore as its JavaScript engine. The sources
> are in the jfx repo,
> along with the JavaFX-specific classes that implement the two-way Java <-->
> JavaScript bridge.
> Other than the public API docs for WebEngine,
WebEngine uses WebKit's JavaScriptCore as its JavaScript engine. The
sources are in the jfx repo, along with the JavaFX-specific classes that
implement the two-way Java <--> JavaScript bridge. Other than the public
API docs for WebEngine, which you referred to in your message, there
isn't any
Wondering which JavaScript engine gets referred to in WebEngine [1].
In case it is currently (JavaFX 14) Nashorn [2], what happens after Nashorn
gets removed from the
next [3] version? In case it is WebKit's JavaScriptCore [4] where can one study
the interface from
WebEngine to it?
---rony
