We developed our application using Dojo in IE8 now we are moving it to IE11.When we run the application, Click event is triggered only for button and check box.When i click on the text box, it does not focuses or any other components.
Any suggestion/help why is it behaving like this.
In the comments you said you're using Dojo 1.9.1. However, when I read the blogpost about Dojo 1.9.2, I see:
Dojo version 1.9.2 is now available for immediate use. The most
prominent changes are:
Support for IE11
Support for W3C Pointer Events API in touch-enabled components (necessary for IE11 support)
Fixes for modern Firefox and Chrome
Fixes to star-mapping and aliases when using built layers
Fixes to sorting Date objects in dojo/store/Memory and other stores that use SimpleQueryEngine
Fixes to Dijit pop-up scrolling when using the scrollbar
Reference: Dojo 1.9.2 and more
Try to run your application with Dojo 1.9.2 first. Since you're already using Dojo 1.9.1, the switch to 1.9.2 should not be too hard I suppose, because it's a patch version.
Related
What is the support for Dojo community support for Dojo 1.8.1 framework?
Our application use Dojo 1.8.1. What is the impact if we are advised to move to the latest framework ?
Dojo 1.x is pretty much "dead" in the sense that only minor maintenance is done.
Migrating to Dojo 2.x or higher from 1.x is not easy, as there is no out of the box migration path.
Of course you can wrap your Dojo 1.x widgets in Dojo 2.x, but then what's the point of using Dojo? Then you can also use another (more widely used) framework.
I don't want to bash on Dojo, as we use it extensively (and successfully) in our company, but the fact that there is no easy migration path to Dojo 2.x makes us want to transition into a more common framework eventually.
More information can be found here: https://github.com/dojo/dojo.io/issues/153
We are currently trying to include Dojo in our liferay 7 application and are running into major difficulties, as it seems the AMD loader is clashing with the AMD loader of Liferay, and its preventing Dojo's define and require from working properly.
If anyone as a solution to getting dojo into Liferay 7 I would appreciate any advice or tips you have for getting this to work.
When using dojo application together with Liferay I could suggest you:
Keep dojo loader requiring only AMD modules from dojo and not Liferay, so use dojo only for dojo and Liferay only for Liferay.
Same when building the application, you need to have two separate build processes, dojo uses it own tools called dojo/util and you won't be able to easily build a dojo app using another builder.
Currently I'm using DOJO 1.9 to develop, but it seems not run on IE. But I see that in the showcase run well with IE. I don't see the version of dojo.js using with showcase. Could you tell me the version of DOJO using in the mobile showcase?
http://demos.dojotoolkit.org/demos/mobileGallery/demo-iphone.html
Thanks!
To check dojo version, open your console and type dojo.version
In this case it's 1.8.0r30226
I've got a simple application using WebKitGTK 1.6.0 that simply displays a webpage in a window.
When I browse a page using it that contains an Ogg/Theora video and HTML5 video element it appears this simple application is using some mozilla plugins and even xulrunner. Can somebody tell me why this is?
Here is a list of files open by the program using lsof.
I built WebKitGTK 1.6.0 and most of it's dependencies from source including gstreamer-0.10 and the gstreamer plugins. No where do I recall configuring WebKitGTK to using any mozilla plugins or xulrunner.
What might be causing the mozilla plugins, libtotem and xulrunner to be loaded? I provided the link to the files the application is using in hopes that it might provide a clue.
Lol, found the reason. I have FireFox, totem and totem-mozplugin installed on my system. Once I removed totem and totem-mozplugin, WebKitGTK used the appropriate Gstreamer plugins to render the video and audio.
I had some application working in Awesomium 1.6.6 but then I upgraded to 1.7 because I needed to add a new functionality to old application which in old Awesomium version wasn't supported.
But now I run in deeper problems, all the API of Awesomium is different. I have changed much things and now my application works but here are the problems i experience.
I have a problem by changing headers: http://pastebin.com/HrgmAJZS in Awesomium 1.7
How i accomplish this in new version?
And I need to change JavaScript on off by clicking the button on a form. I have tried this http://pastebin.com/yU3StmWG but it doesn't seems to work.
Here is my full conversation on Awesomium discussion board: http://bit.ly/Zw3Ldi
Any help appreciated.
There is a known bug, that crashes a WebView or WebControl, when WebPreferences.Javascript has been set to false on the view's WebSession. This will be fixed in the final release of version 1.7.