yes you can convert the image data to base64 and set as html content without need to any extra file or storage or file path etc. img src="data:image/png;base64, iVBOR..rkJggg=="
yes you can convert the image data to base64 and set as html content without need to any extra file or storage or file path etc. Taken from wikpedia
what do you mean by security updates? windows update or firewall/antivirus? we had problems with node32/eset updates and generated some firewall rules (whiltelist exceptions) on the firewall
Thank you for your response. I understood now. Thats why it is not working properly even if setting through System.setProp.. because it is too late. I found this: If an existing application embedds a heavyweight component in a frame, and at the same time installs a custom glass pane, the heavyweight component will disappear. https://bugs.java.com/bugdatabase/view_bug.do?bug_id=6788954 Here we have to manipulate the handling of jxlayer manually until there is a fix to icedtea. (If they plan adding...
thank you four your valuable reply. but i have a question, I already added hardcoded System.setProperty.. in my code. So then even if missed, it should be working. But I have found another interesting clue, I generated a simple project from your default DJBrowser example, but I wrapped the jwebbrowser into a jxlayer (org.jdesktop.jxlayer) which we use in our project for glasspane handling. when run with eclipse (openjdk runtime) it works fine, and when run as batch it works file. But when with openjdk+icedtea...
I have been using dj browse with all versions of oracle on all windows releases without problems. but on adopt openjdk (https://github.com/AdoptOpenJDK/IcedTea-Web) with version openjdk1.8.x we got following problems: as it is known, becasue we use hw with lw objects we set sun.awt.disableMixing to true. If we do not set that we have problems with rendering html objects (they remain gray etc) with openjdk when run without icedtea (through terminal with java exe and classpath) -Dsun.awt.... it works...
Hi. Thanks you for your quick support. When I first encoutered the issue, I tried setting the Dorg.eclipse.swt.browser.IEVersion 10000 or 11000. I had similar issues before this case, where we were setting the content, when I added the X-UA-Compatible meta tag the problem was resolved until this problem. In this case the content generated by BI has already the X-UA-Compatible meta tag at the top of the document. I also tried some meta tag setting after the document has been loaded through executing...
you have to use swt-4.3-win32-win32-x86_64.jar and remove ..win32-x86.jar