It was already announced we'll drop IE 6/7 support after 1.0. I'd like to go further and drop also support for IE8.
By dropping support I mean removing all css/js code that handles IE<=8 issues/deficiencies.
I thought, if one really cares, we could create a plugin that adds support for these versions, but personally I wouldn't spend much time on this.
Opinions?
It was already announced we'll drop IE 6/7 support after 1.0. I'd like to go further and drop also support for IE8.
By dropping support I mean removing all css/js code that handles IE<=8 issues/deficiencies.
I thought, if one really cares, we could create a plugin that adds support for these versions, but personally I wouldn't spend much time on this.
Opinions?
+1
Go ahead and drop it.
Hi,
2014.04.08 11:05, A.L.E.C wrote:
It was already announced we'll drop IE 6/7 support after 1.0. I'd like to go further and drop also support for IE8.
By dropping support I mean removing all css/js code that handles IE<=8 issues/deficiencies.
I thought, if one really cares, we could create a plugin that adds support for these versions, but personally I wouldn't spend much time on this.
Opinions?
+1 as well.
Rimas
2014.04.08 11:05, A.L.E.C wrote:
It was already announced we'll drop IE 6/7 support after 1.0. I'd like to go further and drop also support for IE8. By dropping support I mean removing all css/js code that handles IE<=8 issues/deficiencies. I thought, if one really cares, we could create a plugin that adds support for these versions, but personally I wouldn't spend much time on this. Opinions?
No complaints here, from a sysadmin viewpoint.
Please go ahead...
I think we can finally drop support for old and dirty IE's. From today the Win XP support was ended and the users will be forced to move to new OS with new IE's.
-- *Victor Benincasa* : *Mobile*: +55 (11) 99222-7227 | *Skype*: vbenincasa : *C*hief *T*echnology *O*fficer / *C*hief *I*nformation *O*fficer : Networks, Apps, Systems, Security, High-end support
On Tue, Apr 8, 2014 at 5:05 AM, A.L.E.C alec@alec.pl wrote:
It was already announced we'll drop IE 6/7 support after 1.0. I'd like to go further and drop also support for IE8.
By dropping support I mean removing all css/js code that handles IE<=8 issues/deficiencies.
I thought, if one really cares, we could create a plugin that adds support for these versions, but personally I wouldn't spend much time on this.
Opinions?
-- Aleksander 'A.L.E.C' Machniak LAN Management System Developer [http://lms.org.pl] Roundcube Webmail Developer [http://roundcube.net]
PGP: 19359DC1 @@ GG: 2275252 @@ WWW: http://alec.pl _______________________________________________ Roundcube Development discussion mailing list dev@lists.roundcube.net http://lists.roundcube.net/mailman/listinfo/dev
If the cost of supporting this is merely some additional CSS and JS files, I don't see why IE8 should be dropped.
I am one person who has to use IE8 at work due to several IE8 only internal apps (as do thousands of my colleagues). Granted I have admin rights on my PC and can install Chrome, but not everyone of them does. This is on Windows 7.
IE8 is still young enough to keep around.
Fanen. Please go ahead...
I think we can finally drop support for old and dirty IE's. From today the Win XP support was ended and the users will be forced to move to new OS with new IE's.
-- *Victor Benincasa* : *Mobile*: +55 (11) 99222-7227 | *Skype*: vbenincasa : *C*hief *T*echnology *O*fficer / *C*hief *I*nformation *O*fficer : Networks, Apps, Systems, Security, High-end support
On Tue, Apr 8, 2014 at 5:05 AM, A.L.E.C alec@alec.pl wrote:
It was already announced we'll drop IE 6/7 support after 1.0. I'd like to go further and drop also support for IE8.
By dropping support I mean removing all css/js code that handles IE<=8 issues/deficiencies.
I thought, if one really cares, we could create a plugin that adds support for these versions, but personally I wouldn't spend much time on this.
Opinions?
-- Aleksander 'A.L.E.C' Machniak LAN Management System Developer [http://lms.org.pl] Roundcube Webmail Developer [http://roundcube.net]
PGP: 19359DC1 @@ GG: 2275252 @@ WWW: http://alec.pl _______________________________________________ Roundcube Development discussion mailing list dev@lists.roundcube.net http://lists.roundcube.net/mailman/listinfo/dev
Roundcube Development discussion mailing list dev@lists.roundcube.net http://lists.roundcube.net/mailman/listinfo/dev
On 04/09/2014 06:16 AM, Fanen A. wrote:
If the cost of supporting this is merely some additional CSS and JS files, I don't see why IE8 should be dropped.
No, it's not only additional files. That are also hacks in the code that make code execution and development inefficient. jQuery developers long time ago decided that supporting IE<=8 costs too much and created a separate release branch.
Also, we planned a new responsive skin for Roundcube 1.2. We don't want to care about legacy browsers at that time.
I am one person who has to use IE8 at work due to several IE8 only internal apps (as do thousands of my colleagues). Granted I have admin rights on my PC and can install Chrome, but not everyone of them does. This is on Windows 7.
But I hear you. It looks the compat. plugin is a need.
On 14-04-08 11:42 PM, A.L.E.C wrote:
On 04/09/2014 06:16 AM, Fanen A. wrote:
I am one person who has to use IE8 at work due to several IE8 only internal apps (as do thousands of my colleagues). Granted I have admin rights on my PC and can install Chrome, but not everyone of them does. This is on Windows 7.
But I hear you. It looks the compat. plugin is a need.
we (tucows/opensrs) are in the process of switching over to roundcube and are looking to contribute back to the project. we have many legacy IE7 users as well as IE8 users - so we'll want to maintain IE7 compatibility as well as IE8 compatibility. given that we were essentially going to have to create an IE7 compat plugin anyway, assisting on an IE8 compat plugin seems like a good place for us to start contributing. we're happy to help in splitting this off into a separate plugin and maintaining it (which does seem like the best way to handle any non-standards compliant browsers).
On 04/11/2014 08:10 PM, Brendan wrote:
assisting on an IE8 compat plugin seems like a good place for us to start contributing. we're happy to help in splitting this off into a separate plugin and maintaining it (which does seem like the best way to handle any non-standards compliant browsers).
I took a look at this again and it doesn't look very hard, so I'll create a base for the plugin soon. I'll let you to know.
On 04/12/2014 08:51 AM, A.L.E.C wrote:
I took a look at this again and it doesn't look very hard, so I'll create a base for the plugin soon. I'll let you to know.
This is done in git master. I moved already most of the code to the plugin. There are left two small javascript hacks that I'll move later.
The plugin is legacy_browser. I took a look at IE7 and IE8 and saw a few issues. So, now is time for those of you who care about these browsers to test and provide patches (pull requests).
Am 08.04.2014 10:05, schrieb A.L.E.C:
It was already announced we'll drop IE 6/7 support after 1.0. I'd like to go further and drop also support for IE8.
By dropping support I mean removing all css/js code that handles IE<=8 issues/deficiencies.
I thought, if one really cares, we could create a plugin that adds support for these versions, but personally I wouldn't spend much time on this.
Opinions?
From my point of view, this is not a good idea. Unless you want to make RC
unusable for those who are still running XP and are not allowed to install FF or any other browser on their own (for instance and especially in corporate environments).
I'm not sure if it is really true, but I have read that approx. 30% of all Desktops are still running XP and IE 6-8:
http://www.pcworld.com/article/2140840/windows-xp-chronicle-of-a-death-foret...
Plus that the British and the Dutch government have closed service contracts for XP with Microsoft:
http://www.zdnet.com/dutch-government-pays-millions-to-extend-microsoft-xp-s...
Not to speak about the home users who are using a Laptop or Desktop PC which is hardware-wise simply not capable of running Win7 or Win8, and who can't (or want to) afford a new machine.
I understand that it's a major hassle to support this old stuff, though...
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
On Wed, Apr 09, 2014 at 12:46:19AM +0200, Michael Heydekamp wrote:
Am 08.04.2014 10:05, schrieb A.L.E.C:
It was already announced we'll drop IE 6/7 support after 1.0. I'd like to go further and drop also support for IE8.
By dropping support I mean removing all css/js code that handles IE<=8 issues/deficiencies.
I thought, if one really cares, we could create a plugin that adds support for these versions, but personally I wouldn't spend much time on this.
Opinions?
From my point of view, this is not a good idea. Unless you want to make RC unusable for those who are still running XP and are not allowed to install FF or any other browser on their own (for instance and especially in corporate environments).
+0
7% of our users are still using IE8, that's representative a many thousands of users for us. That said, they could use Squirrel Mail instead of Roundcube so it wouldn't be a huge problem for us if IE8 support was dropped but not everyone may have the luxury to run multiple applications for their users.
On 2014-04-08 03:05, A.L.E.C wrote:
It was already announced we'll drop IE 6/7 support after 1.0. I'd like to go further and drop also support for IE8.
By dropping support I mean removing all css/js code that handles IE<=8 issues/deficiencies.
I thought, if one really cares, we could create a plugin that adds support for these versions, but personally I wouldn't spend much time on this.
Opinions?
I can see the attraction of EOL'ing IE8 support, but wishing for XP/IE8 to go away is pretty futile right now, especially outside the first world.
I'd vote (as a service provider admin) to either leave IE8 support intact, make the IE8 compatibility stuff a selectable plugin for people who need to continue to support XP users, or as a last option declare a stable "legacy support" version that'd get no feature and only security (if necessary) updates through some defined date (12/31/2015?).
One of our larger customers is an ISP in India, and an alarming percentage of their userbase is on IE8 still, and I don't foresee that changing in the next several months.
--Mike Gilday Redpin.com
On 04/09/2014 01:28 AM, duchamp@redpin.com wrote:
I'd vote (as a service provider admin) to either leave IE8 support intact, make the IE8 compatibility stuff a selectable plugin for people who need to continue to support XP users, or as a last option declare a stable "legacy support" version that'd get no feature and only security (if necessary) updates through some defined date (12/31/2015?).
We "marked" 1.0 as LTS and I think we'll support it for so long. The IE8 support drop is planned for future versions (and 1.1 will be released somewhere around a new year).
One of our larger customers is an ISP in India, and an alarming percentage of their userbase is on IE8 still, and I don't foresee that changing in the next several months.
So, we'll most likely create an official plugin hoping people interested will provide feedback/support/fixes for it.
One of our larger customers is an ISP in India, and an alarming
percentage of their userbase is on IE8 still, and I don't foresee that changing in the next several months.
So, we'll most likely create an official plugin hoping people interested will provide feedback/support/fixes for it.
That sounds like a perfect solution, and you seemingly have already one party with a large customer in Indian who can provide help in maintaining such a plugin :)
Cor