FYI, using http://selectivizr.com/ in ComparisonDashboard to get CSS3 selectors to work (in JavaScript & in stylesheets).

Well, since version 2.1.0 IE8 is a messup just after "Logout" link.

Maybe the best choice would be handling unsupported browsers with an exception.

I haven't tested recently, but are you saying Piwik does not work well under IE8?

Yes, is not useful, we will deliver Firefox to all users. Open source wins.
In the meantime I took a screenshot, it's Piwik 2.2.3b3 rendered with IE8

Attachment: Piwik 2.2.3b3 as seen by IE8
piwik-ie8.png

Hi tassoman,

I test Piwik with IE8 regularly and it works for me with latest beta and with 2.1.0.

• Can you try to clear the cache in IE8? See https://kb.wisc.edu/page.php?id=12314 for more help
• From what I understand it works with Firefox. If not, can you try to remove all files within the "tmp/assets/" and "tmp/templates_c/" directories? If you don't know how to do this you might want to consider installing the http://plugins.piwik.org/cacheBuster "CacheBuster" plugin within your Piwik under "Settings => Marketplace => Get new functionality"
• In case you use any custom plugins, disable them and see if the error is still there
• Maybe you can also check whether http://demo.piwik.org works for you with IE8?

I got it. The problem is my IE8 configuration runs intranet websites in compatibility mode. So that can't render AngularJS stuff very well.

Agente utente: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3)
Timestamp: Wed, 14 May 2014 08:25:09 UTC
Messaggio: [$sce:iequirks] http://errors.angularjs.org/1.2.13/$sce/iequirks
Linea: 255
Carattere: 252
Codice: 0
URI: http://vmdev.local/piwik/index.php?module=Proxy&action=getCoreJs&cb=cccc8f48b7e4934285d6711b0081b516

I've removed the flag from "run intranet websites using compatibility mode" and the render was ok.

The problem is I can't modify this option to all dozens users of the intranet.

I've found a post on MSDN describing how to handle this by sending html tags in the head section of the page but I'm not really sure it will help.

but I'm not really sure it will help.

To try it you can edit the file: https://github.com/piwik/piwik/blob/master/plugins/Zeitgeist/templates/dashboard.twig#L10-10

and put the meta tag there. Then you should see the meta tag in the "Analytics report" in Piwik (but not on login screen or admin). Maybe it could make Piwik work well under IE8 for you?

Looking at dashboard.twig template I've discovered you've already set the X-UA-Compatible tag and is set to IE=EDGE. By the way I've tried the hack but doesn't works.

So I prefer to go with no hack. Intranet compatibility is a internal setting of IE and so can't be edited by html headers.

Well, going deeper into the IE deal I've sorted out there's a crazy bug in IE9 that makes it ignore the UA-Compatible meta tag when conditional comments are placed before it.

So that, I've hacked badly* dashboard.twig and admin.twig files removing conditional comments in html source and now IE8 it's flawlessly working also on my Piwik dev machine inside the intranet.

(* I promise to git reset --hard my local branch)

That's a good point. Once we remove support for IE8 we can remove the conditional comments as well and you won't have to patch it anymore ;)

Good, thanks. Just keep in mind this bug is also affecting IE9 also

Replying to tassoman:

Well, going deeper into the IE deal I've sorted out there's a crazy bug in IE9 that makes it ignore the UA-Compatible meta tag when conditional comments are placed before it.

So that, I've hacked badly* dashboard.twig and admin.twig files removing conditional comments in html source and now IE8 it's flawlessly working also on my Piwik dev machine inside the intranet.

(* I promise to git reset --hard my local branch)

@tassoman I've created a ticket here: #5282 Include Meta tag IE=edge for best security practises

Maybe you have some comment about it? It was sent to us by email to our security email

@tassoman maybe this stackoverflow thread is related: http://stackoverflow.com/questions/6156639/x-ua-compatible-is-set-to-ie-edge-but-it-still-doesnt-stop-compatibility-mode

Replying to matt:

@tassoman maybe this stackoverflow thread is related: http://stackoverflow.com/questions/6156639/x-ua-compatible-is-set-to-ie-edge-but-it-still-doesnt-stop-compatibility-mode

Yes Matt, it's the same stuff I mentioned in comment nr.13, as you can see in the second StackOverflow most valued reply they suggest to go straight with doctype and html declaration without any conditional comment before the html and meta tag.

The first reply is about ISS7/9 but we haven't that environment so can't be helpful.

What is the current state on supporting IE8? In ticket August 2014 is mentioned. We have October 2014 soon. Can we drop support for IE8? Would like to work on #6283 To make it work on IE8 and lower we would have to somehow call document.createElement('custom-element'); for each element which is kinda annyoing. @mattab ?

Hard to take the decision here as it would simply shut down Piwik for some corporations. Though we must do it at one point. What is status at AngularJS project support of IE8? as long as AngularJS works well on IE8 I reckon we should try to support it... unless it becomes really too time consuming...

Well, as Piwik user I can say for my organization, in my SSO custom plugin I'm checking that user-agent isn't MSIE by regular expression, then forcing them logging in using a different browser throwing an handled exception while at login.

Maybe this would be a community question you could solve using a poll. Can't say if integrating a 3rd parties poll plugin in core would be a good idea for tasting users opinion about a subject.

Imagine something of a small tip popping up to superadmins, just like the "New piwik update is available" thing bringing a link to the survey in a new browser tab...

Not sure about this poll. I reckon the result would be something like IE8 users voting to still support and non IE8 users will probably not really care whether we still support it or not. A problem is that we do not know how many of our users are still using IE8. We can delay #6283 but should definitely start working on it once we also start to work on using angular routes and when using it for visualizations.

AngularJS 1.2.* should still support IE8. AngularJS 1.3 will drop support for IE8 and should be released soon I reckon. At least there is already an 1.3-RC3

I'm closing this one, but not be afraid Piwik 2.X which will be supported for more than a year from now on will be compatible with IE8. Closing this issue as support will be dropped in 3.0

Actually I will reopen as there's more to do:

• Changelog
• Update some code blocks where we can now use .finally() instead of ['finally'] etc

fixed via #8591. As mentioned we still support IE8 for a pretty long time but in Piwik 3.0 it will be removed.