@mattab opened this Issue on February 4th 2014 Owner

At some point we should drop IE8 support.

As of January 2014 there are only ~10% of all users using IE8. On Piwik.org, we are seeing 1.3% using IE8.

Reasons:

  • This is causing extra work for cross browser testing, development, troubleshooting.
  • Since we are considering using AngularJS, and their latest version 1.3 drops IE8 support, and for other reasons, we would like to drop IE8 support.
  • In April 2014, Microsoft will be ending support for Windows XP, which means the end of support for the operating system most of Internet Explorer 8 users use.

Note:

I think we should support IE8 at least until August 2014 to give companies a few months to react after MS drops XP support.

@tassoman commented on May 13th 2014 Contributor

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

@diosmosis commented on March 5th 2014 Member

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

@tassoman commented on May 12th 2014 Contributor

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.

@mattab commented on May 13th 2014 Owner

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

@tassoman commented on May 13th 2014 Contributor

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

@tsteur commented on May 14th 2014 Owner

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?
@tassoman commented on May 14th 2014 Contributor

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.

@mattab commented on May 15th 2014 Owner

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?

@tassoman commented on May 15th 2014 Contributor

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.

@tassoman commented on May 28th 2014 Contributor

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)

@tsteur commented on May 28th 2014 Owner

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 ;)

@tassoman commented on May 29th 2014 Contributor

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

@mattab commented on June 2nd 2014 Owner

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

@mattab commented on June 4th 2014 Owner
@tassoman commented on June 4th 2014 Contributor

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.

@tsteur commented on September 24th 2014 Owner

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 ?

@mattab commented on September 24th 2014 Owner

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...

@tassoman commented on September 25th 2014 Contributor

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...

@tsteur commented on September 25th 2014 Owner

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

@mattab commented on October 21st 2014 Owner

I've added Request For Comments label to gather feedback from users. We would like to drop IE8 support this year or early next year. Thoughts?

@ThaDafinser commented on October 22nd 2014 Contributor

+1 from here, _but for directly IE9 support drop too_. Then Piwik can use real HTML5 features:
http://caniuse.com/#compare=ie%2B8%2Cie%2B9%2Cie%2B10%2Cfirefox%2B36%2Cchrome%2B41

(And i'm using Piwik in a company, there still IE8 is used widely...but everybody can use FF portable or Chrome to switch)

http://googlesystem.blogspot.com/2013/11/google-drops-support-for-ie9.html

@tassoman commented on October 22nd 2014 Contributor

Our situation is similar, more, we're a government administration slowly switching to open source.
So we took advantage of Piwik to accelerate the browser switch to Firefox.

But you see, all clients still have IE8-9 installed "also" in Win7 environment.

@gaumondp commented on October 22nd 2014

My instinct is that it would be safer to make it (droping IE8) part of Piwik 3.0 release...

So it would becomes quite easy to say: You need PHP 5.3.3 and can't update it or you're forced to use IE8 ? Then the "solution" is to stay below Piwik 3.0.

And maybe introduce right now a config setting like : "dont-update-higher-than-version2.99 = 1". So it disable automatic update. People in a situation where IE8 is still alive would be able to not make the mistake of upgrading to Piwik 3.0 when available...

@ThaDafinser commented on October 23rd 2014 Contributor

@gaumondp pls do not stick the browser support together with the piwik major version! Development is all the time already limited/sticked with the PHP version....which is enough :-1:

Watch the stats i posted...IE8 is more used than IE9, so drop them together makes sense, since the frontend can be improved so nicely then with real HTML5....

@sgiehl commented on October 23rd 2014 Member

I guess what @gaumondp ment, was to drop support with a new major version. I think that makes sense, as we should not drop support with any minor release.

@ThaDafinser commented on October 23rd 2014 Contributor

@sgiehl dropping compability layer (meaing: removing of all IE8/IE9 hacks) in the next major version is good. But you could just stop testing/supporting IE8/9...so if it works ok, but problems wont be solved anymore.

@gaumondp commented on October 23rd 2014

Yes @sgiehl, what I was trying to say is make it easy for everyone to know that from Piwik 3.0 and up, support for IE8 (and IE9 if you want) AND PHP 5.3 was dropped.

  • Forced to use IE8 ? Can't update to PHP 5.4 or more (stuck with Ubuntu LTS 10.04 for example):
    Solution: Keep your Piwik at version 2.8.x
  • You can upgrade ar are already using PHP5.4 and up? No browsers restrictions? : Use Piwik 3.x and up.

@ThaDafinser, I'm in the same situation as @tassoman where people are "forced" to use a browser and don't have admin rights to use anything else. Running old legacy stuff where you can't update or use what you want if you're not in IT is not pretty...

You can give me all the stats you want, it will not be possible to upgrade for some people. Even the Piwik fast track with almost 10 releases a year is not something everybody can live with. People with a little 1000 pageviews a day won't bother and upgrade twice a day if they want using the web interface but with millions pageviews, you don't take those kinda risks.

So again I'm all in for dropping support for IE8, IE9 and PHP 5.3. I don't need my own suggestion ("dont-update-higher-than-version2.99 = 1"). I'm aware of the situation but most Piwik users never went here on Github, never read install instructions (how many time have we seen "why Piwik doesn't work in my PHP 5.2 in the Forums?). I just proposed to make it easier for the laymen Piwik users.

:)

@tassoman commented on November 28th 2014 Contributor

My organization is spreading IE9 on Win7 machines, I've got it also :unamused:

@CanuckNick commented on December 1st 2014

We are using IE8 on Windows 7 and the Piwik interface does not work. We already have to tell users to use Chrome or Firefox.

@bglxx commented on December 1st 2014

I had the same prob a few weeks ago because I want to minimize the efforts for testing and debugging, but, unfortunately, there are a lot of systems working with old software. Approx. 10% with Win-XP and also 10% with IE-8. This ratio is decreasing very slow.

My first attempt was to say: Outdated software is typical for private PCs or bad maintained infrastructure in very small comanies.

That's wrong and I've found some large international companies working with IE-8.

My decision - and I dont like the consequence - is to support IE-8 at least until 2016. If it falls below one or two percent, we will stop support.

@ThaDafinser commented on December 2nd 2014 Contributor

TL:DR version (deleted my long post)

If you _need IE8-9 support_ stick with your current Piwik version.
If you want _shiny new features, update your IE_

Both is not possible. _But please guys let Piwik move forward_.....there are already so many applications in the internet which doesnt work anymore with IE8...

@asafyish commented on January 7th 2015

Are we talking about Piwik Dashboard or piwik.js ?

@sgiehl commented on January 7th 2015 Member

Piwik Dashboard for sure. piwik.js should always be compatible with as many browsers & versions as possible.

@mattab commented on August 13th 2015 Owner

when #8443 will be merged, effectively IE8 support will be dropped.

Let's announce it in Developer changelog as well as in the future Piwik 3 changelog of course.

@tsteur commented on August 18th 2015 Owner

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

@tsteur commented on August 18th 2015 Owner

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
@tsteur commented on August 20th 2015 Owner

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

This Issue was closed on August 20th 2015
Powered by GitHub Issue Mirror