Explorer 11 goes to fallback page when project built as "FINAL".

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.

    This is weird. My e-card project seemed to work perfectly fine while I was in development.

    Today, I built it as a HTML5 Final Project, put it on the same server, but now, Internet Explorer (version 11) goes to the fallback page, like it doesn't support HTML5.
    If I build the project again in development mode, replace the "final project" files with the "development" ones, then it starts working again and doesn't go to the fallback page.

    So same project, work when built as "HTML5 development", but goes to fallback page if built as "HTML5 final project".

    Chrome works fine. Other browsers too. Only IE seems to act like this when project is built as "final".

    I'm on 283.2. Anyone else experienced a similar issue?

    Update to 283.5

    Project work in Internet Exlorer 11 when run localy through "build and run" function.
    But when I take the exact same files and put them online, Internet Explorer defaults to the fallback page like it isn't supporting HTML5, even though all worked well in "build and run".

    It isn't a server problem either, as everything works fine in Chrome, both locally and online.

    Only Internet Explorer, somehow, always end up going to the fallback page, even if it supports HTML5.

    Is there something I'm missing? Is there a way to fix that by editing the index.html page or any javascript file?

    Ok. I found the problem.

    The company I work for as an intranet. And their intranet site only works with IE when it is set to "compatibility view" (Completely stupid as it runs on Sharepoint, which in theory should work fine with other MS products but that doesn't seem to be the case). So on all our machines, the intranet domain is running in compatibility view mode by default. And since our internet website is part of the same domain, IE also display anything coming from our website in "compatibility view". IE, when set to compatibility view, doesn't process HTML5 functions. Or at least, doesn't process the <canvas> tag.

    So anyone, just take note that if someone is running your HTML5 app in IE in compatibility view (even if the IE version you're using support HTML5), it will jump to the fallback page.

    I don't know if this was already written (or discussed) somewhere, if it was, I'm sorry for bringing this up again. I just thought the info would be good to share.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login