Openlaszlo embed.js issue - migration

I have a application where ctrl + s key combination is handled. So when i press this key a new screen appears with some details. This is working fine in mozilla FF 15.0 and 16.0 but when i am viewing it in an AIR web browser runtime 3.4 in full screen mode, the browser is getting minimized and the screen is also not appearing properly.
And later i discovered that when i was using the embed.js file of OL 3.3 version i am not facing this issue the air browser is working fine. But when i am using the latest embed-compressed.js i am getting this. Any idea why this is happening ?
I am using Openlaszlo 5.0.x this issue is also happening in OL 4.9's script

Related

Latest Safari Browser issue with jPlayer

I am using jPlayer to play videos in one of my existing project. Everything works fine with Windows OS(in all browsers). Everything was also working fine in older Safari versions as well(in MAC OS). All of a sudden, in latest Safari version(in 13.1), videos are not playing and following error is generated in console panel.
I have also disable auto play option as well as per the latest guidelines. Any idea what could be wrong and how to detect issue?
I have experienced also some problems with the latest IOS. Updating the jplayer lib to latest 2.9 solved the issue.

Fabric js not working on IE 11

I have created whiteboard with fabricjs and javascript. It works fine in chrome and firefox but all of fabricjs functions does work in Edge but not working on IE 11 it is completely blank. How can I fix this problem?
My fabric version is 2.2.3.
internet-explorer-11 fabricjs whiteboard

Render camera preview in Chrome using Native Client SDK

I'm trying to write ppapi plugin for Chrome which will use webcam (show preview and write file). I have installed NaCl sdk with pepper_35.
There available examples in /examples/api/ folder: media_stream_audio and media_stream_video.
The audio example works fine - requests access to microphone and shows some kind of preview.
The "media_stream_video" example must show web-camera video preview, but when I load example on the local web server (with make serve command), there appears red rect, and Chrome asks for the web camera access. When I click “allow” - webcam indicator lights-up, chrome show that web page uses the web camera, and I see the camera settings icon. But the preview doesn't work, there still red rectangle instead.
I checked this on Windows 8.1, Windows 7 and Mac OS X, with five different webcams, and have no idea what can be wrong.
Maybe someone already encountered with the same problem?
Installing the pepper_37(dev) version of NaCl SDK solved the problem. Looks like it is unstable version currently, but it works.

Javafx webkit loading HTML content

I have a javafx application which is loading HTML content using webkit. I have created a stage and a scene and do webEngine.load(html). It works fine. But when I minimize the application and then again maximize it after sometime, the stage shows black screen for 2-3 seconds before loading the html again.
My question is why is this happening and how can I avoid this?
Thanks,
Nitin
You are using very old JavaFX. Can you try with latest version 2.2.21 which can be found here:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
It's cobundled with jdk 7u21, just download and install jdk and you get JavaFX with it.

In Vaadin PDF does not work in popup Window

I am trying to display a PDF in a popup window using Vaadin 6.6.2 and the code as shown in this blog:
http://jcraane.blogspot.com/2010/09/printing-in-vaadin.html
The problem I have is that whenever I close the Window containing the PDF it always hangs the current browser tab in IE 9.
I have tested this in Safari, Firefox, and IE 8 and its works fine. I also know that the problem is related to the embedded PDF as I have tried replacing the embedded PDF with a Vaadin Label and then the popup window closes fine in IE9.
I had a similar problem in Firefox 3.x, I solved it by upgrading to Firefox 4, and upgrading the Adobe plugin.
It seems to me the problem is on the browser/plug-in side.
If you are stuck with that browser/version, try just upgrading the plugin if that's not already on the latest version.