Re: [JDK-8223377] Updated information - Webengine crashes when HTML contains japanese/sundanese punctuation code points

2019-05-10 Thread Kevin Rushforth
The normal submission process yielded a bug report to be evaluated, and it's still in the queue to be looked at. Since you provided some additional information, we can add it to the bug report as a comment. Btw, the direct URL for the bug in JBS is:

[13] RFR: JDK-8223719: Add .gitignore to repo

2019-05-10 Thread Kevin Rushforth
Simple fix to add a .gitignore file to the upstream HG openjfx/jfx-dev/rt directory. This file currently exists as a "javafxports-only" file in the javafxports/openjdk-jfx sandbox on GitHub. https://bugs.openjdk.java.net/browse/JDK-8223719 http://cr.openjdk.java.net/~kcr/8223719/webrev.00/

Re: set Destination attribute in printReqAttrSet

2019-05-10 Thread Neacsu Cristian
Damn ... Thank you for your reply and for the ticket submitted. I created an invoice application for my own company, and imagine that java 9+ would kill me :) All the invoices are generated automatically through pdf printer (I tried few free pdf libraries as an alternative, but for what I need

[JDK-8223377] Updated information - Webengine crashes when HTML contains japanese/sundanese punctuation code points

2019-05-10 Thread Matthias Bläsing
Hello, as the normal submission process did not yield an update for the above mentioned issue and this is a crasher, I try to get the information submitted here. As reference the JDK issue: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8223377 Summary: I experimented with OpenJFX

set Destination attribute in printReqAttrSet

2019-05-10 Thread Neacsu Cristian
For windows print through "Microsoft Print to PDF", there is no way right now to pre-define a path programmatically. There is no way to set inside the printReqAttrSet (J2DPrinterJob), an attribute of type Destination, to solve this issue. Before jdk 9, I was bypassing it through reflection like

Re: set Destination attribute in printReqAttrSet

2019-05-10 Thread Philip Race
Everything you are touching there pre-supposes knowledge of today's implementation of the JavaFX printing API, so I don't think we can endorse that. The right thing to do (maybe years ago!) is to file an RFE to request that something like the Destination attribute be supported in the FX printing