This topic contains 5 replies, has 3 voices, and was last updated by  pauld 1 week ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    IE 11 Posts
  • IE 11 #80054

    AA5MC
    Participant

    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?

    IE 11 #80061

    AA5MC
    Participant

    Okay I had to add <meta http-equiv=”X-UA-Compatible” content=”IE=edge” />
    to my index page all works now!

    IE 11 #80074

    Peter Stoev
    Keymaster

    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

    IE 11 #106713

    pauld
    Participant

    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

    IE 11 #106715

    Peter Stoev
    Keymaster

    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

    IE 11 #106726

    pauld
    Participant

    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!

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.