This topic contains 5 replies, has 3 voices, and was last updated by pauld 5 years, 1 month ago.
Viewing 6 posts - 1 through 6 (of 6 total)
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic.
jQuery UI Widgets › Forums › General Discussions › IE 11
This topic contains 5 replies, has 3 voices, and was last updated by pauld 5 years, 1 month ago.
hello,
I’m using the jqxTree, jqxInput and jqxGrid components on my site.
I tested it with Chrome and Firefox( latest version) works great but for IE 11 nothing is rendering? do I have to do something different to get my components to rendering under IE 11?
Okay I had to add <meta http-equiv=”X-UA-Compatible” content=”IE=edge” />
to my index page all works now!
Hi AA5MC,
Actually, adding meta tags is not necessary, too. I suggest you to look at our online demos. We don’t use such meta tags and the widgets still work fine.
Best Regards,
Peter Stoev
jQWidgets Team
http://www.jqwidgets.com
Hi,
We have a user who is using IE11 and is also having a problem with widgets not rendering. There are no errors in the console and other IE11 users do not have the same issue. IE11 reports that it’s in Edge mode, yet it’s behaving as if it’s in an older mode — e.g. I can recreate the symptoms if I manually toggle the mode to 10 or lower.
Meanwhile, we noticed that the online demos (e.g., tabs demo) now have the following tag: <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
Is that now necessary under certain conditions?
Thanks
Hi
The meta tag means IE11 to display content in the highest mode available.
We are mot sure what your client”s issue is with IE11. Pleaee, send us an example in jsfiddle or other similar online playground and we will take a look.
Regards
Peter
Hi, Peter
Thanks for your quick response. Today, we’ve found that the issue for the user in question seems to be site specific. E.g., everything works as expected when he tests the app in our SAAS environment, but it does not work as expected when accessing it in a client’s on-premise environment. Now we are wondering if the client’s Tomcat configuration may be messing with the http headers — if you have any suggestions on what to look for, that would be very helpful.
Thanks!
You must be logged in to reply to this topic.