[webkit] [9] Review request for 8089842: JavaScript2Java Bridge: A char value cannot be set from JavaScript

Hi Kevin, Alexander, Guru, Please review the below patch. JIRA: https://bugs.openjdk.java.net/browse/JDK-8089842 Webrev: http://cr.openjdk.java.net/~arajkumar/8089842/webrev.00/ Issue: There is no way to JS character as a Java Char type. Fix: There is no Char type in JavaScript, but we can

[8u] review request: 8139326: [TEST] Unit tests for JFXPanel with security manager don't detect errors

Hi Chien, Can you do a quick sanity test review of the backport to 8u-dev of the following: https://bugs.openjdk.java.net/browse/JDK-8139326 http://cr.openjdk.java.net/~kcr/8139326/webrev.00/ This was earlier reviewed (by you) for 9-dev with the intent to backport to 8u-dev, but the

[8u] review request: 8139326: [TEST] Unit tests for JFXPanel with security manager don't detect errors

Hi Chien, Can you do a quick sanity test review of the backport to 8u-dev of the following: https://bugs.openjdk.java.net/browse/JDK-8139326 http://cr.openjdk.java.net/~kcr/8139326/webrev.00/ This was earlier reviewed (by you) for 9-dev with the intent to backport to 8u-dev, but the

[9] Review request: 8153872: Nashorn no longer needs access to com.sun.javafx.application

Jim, Please review the following fix: https://bugs.openjdk.java.net/browse/JDK-8153872 http://cr.openjdk.java.net/~kcr/8153872/webrev.00/ This is a simple backout of the earlier fix for JDK-8153754. -- Kevin

Changes for April 2016 CPU release (8u91/8u92) synced into FX 8u-dev and 9-dev

I have synced the OpenJFX changes from the just-released April 2016 CPU release (8u91/8u92) into 8u and into 9. Here is a webrev of the FX 8u92 changes for those who are interested in the changes, but don't want to wade through the 52 separate changesets I just pushed (most of which are tag

Re: What does this mean for the future of JavaFX on iOS?

Hi, in my opinion the abandonment of RoboVM is a very big step back for Java on Mobile because there is NO real alternative to RoboVM. So it has definitely a big impact on Gluon and JavaFX on Mobile. Gluon uses RoboVM 1.8 - and old version of RoboVM which will be not developed anymore. So no

Re: What does this mean for the future of JavaFX on iOS?

Well I did ask Johan what AOT they are going to use instead of RoboVM but there has not be a response yet. Let's face it, without highly optimised AOT, Java and/or JavaFX on mobiles is simply not viable which in turn implies that JavaFX itself is not even worth looking at... RIP. But I take

Re: [9] Review request for 8150076: Print jobs are not finished when used a page range

Hi Phil, Please see my update in jbs: https://bugs.openjdk.java.net/browse/JDK-8150076 Thanks, Mikhail. On 4/14/2016 12:28 AM, Phil Race wrote: I have an old PageRange printing test where I set settings.setPageRanges(new PageRange(1,3)); and it prints fine on