Hi Steve,
You're correct, WebView doesn't include all the features that WebKit provides. This is configured at
a compile time with a set of preprocessor definitions.
The reason is that a feature may not work from scratch for WebView and may require additional code
changes in WebView port. So, every feature should be explored before including into WebView.
Regards,
Anton.
On 25.06.2015 7:39, Steve Hannah wrote:
To sort of answer my own question, I found out that the JavaFX webview is
missing quite a few APIs that are present in Webkit. This is the result of
the HTML test I ran:
https://html5test.com/s/71bdbe284015d02b.html
This gives me a starting point so I can create polyfills if I want to move
forward.
Steve
On Wed, Jun 24, 2015 at 8:41 AM, Steve Hannah <st...@weblite.ca> wrote:
I have a javascript app that is not loading in the JavaFX webview (JDK8).
User agent string indicates WebKit 537.44, so I downloaded the nightly
build for WebKit 537.44 to test, and the app works in that.
No errors are reported in the webview (I've hooked up change listeners,
error listeners, etc...), and I hooked up Firebug lite - but it also
doesn't report any errors -- likely either errors are occurring before the
page is loaded (i.e. before Firebug lite is added).
Does WebKit 537.44 use the exact same Javascript engine as the WebView
that reports 537.44 as the webkit version - or are there some differences?
--
Steve Hannah
Web Lite Solutions Corp.
