[Trac-dev] Internet Explorer support in Trac 1.3.1 and later

[RjOllos]

We've been preparing API Changes (1) in advance of the start of 1.3.x
development in order to determine what versions of dependencies we'll
support. However, we haven't defined which browser versions we'll support.
On the API Changes page I suggested that we following the browser support
outlined by jQuery (2).

However, I read today that Microsoft is dropping support for IE < 11 (3).
Is there any good reason we shouldn't do the same, effective Jan 12th, for
*all* Trac versions? I suppose we could fix critical issues and critical
bugs, but anything else seems like a waste of our time if Microsoft isn't
even patching the browser.

- Ryan

(1) http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.3#ModifiedDependencies
(2) https://jquery.com/browser-support/
(3) http://www.theverge.com/2016/1/6/10722426/internet-explorer-8-9-10-dying

[Tim Graham]

Sounds good to me. You wouldn't intentionally break support in already
released versions of Trac, just no longer fix new issues, correct?

As a data point, Django 1.9 (released Dec 1, 2015) switched to jQuery 2.x
which has the same API as jQuery 1.x, but does not support Internet
Explorer 6, 7, or 8, allowing for better performance and a smaller file
size.

By the way, is this statement on (1) that you linked correct? "These notes
reflect the current status for 1.3.1
<http://trac.edgewall.org/milestone/1.3.1>, in trunk
<http://trac.edgewall.org/browser/trunk>​" That seems to suggest that trunk
is open for changes for the 1.3.x series, but as far as I know, it's still
1.1.x. Maybe I misinterpreted... I would still like to help out with Python
3 support when the time is right.

Post by RjOllos
We've been preparing API Changes (1) in advance of the start of 1.3.x
development in order to determine what versions of dependencies we'll
support. However, we haven't defined which browser versions we'll support.
On the API Changes page I suggested that we following the browser support
outlined by jQuery (2).
However, I read today that Microsoft is dropping support for IE < 11 (3).
Is there any good reason we shouldn't do the same, effective Jan 12th, for
*all* Trac versions? I suppose we could fix critical issues and critical
bugs, but anything else seems like a waste of our time if Microsoft isn't
even patching the browser.
- Ryan
(1)
http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.3#ModifiedDependencies
(2) https://jquery.com/browser-support/
(3)
http://www.theverge.com/2016/1/6/10722426/internet-explorer-8-9-10-dying

[RjOllos]

Post by Tim Graham
Sounds good to me. You wouldn't intentionally break support in already
released versions of Trac, just no longer fix new issues, correct?

Thanks for the feedback. I'm just proposing to no longer fix new issues for
IE < 11.

Post by Tim Graham
As a data point, Django 1.9 (released Dec 1, 2015) switched to jQuery 2.x
which has the same API as jQuery 1.x, but does not support Internet
Explorer 6, 7, or 8, allowing for better performance and a smaller file
size.
By the way, is this statement on (1) that you linked correct? "These notes
reflect the current status for 1.3.1
<http://trac.edgewall.org/milestone/1.3.1>, in trunk
<http://trac.edgewall.org/browser/trunk>​" That seems to suggest that
trunk is open for changes for the 1.3.x series, but as far as I know, it's
still 1.1.x. Maybe I misinterpreted... I would still like to help out with
Python 3 support when the time is right.

The trunk is still 1.2dev. I'm working on wrapping up 1.2 development and
look forward to working with you on adding Python 3 support.

- Ryan