Drop support for IE6 and earlier browsers from code
It is no longer necessary to provide support fro IE6 and earlier. There is some code that specifically refers to this that should be removed. We might also want to consider including warnings for any IE6 users, and a link to instructions for upgrading the browser. In my view this is good and helpful practice and is easily done.
Blueprint information
- Status:
- Complete
- Approver:
- webtrees team
- Priority:
- Medium
- Drafter:
- kiwi
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- kiwi
- Completed by
- kiwi
Related branches
Related bugs
Sprints
Whiteboard
I would avoid doing anything significant merely to benefit IE6, but I wouldn't be in a hurry to remove existing support.
Logs of sites I work with show that (believe it or not) IE6 is still more than 45% of the visitors!
If IE6 visitors could be persuaded to upgrade, that would be good, but I'm not sure it's possible.
Too many words, and they won't read it; too in-your-face and they'll get angry and go elsewhere.
[kiwi]
A bit too late I'm afraid wes. Off-line the development team decided to do this right from the start of webtrees. Changes have already been made (mainly in themes) that effectively render webtrees almost unusable in IE6. No new changes are / will be tested in IE6 either. The only thing we haven't done is actually remove some of the old IE6-based clutter left from PGV.
Must be strange sites you use though. I've seen some variations in IE6 usage report, from <7% to around 20% - but nothing as high as 45%, except perhaps in large corporate organisations. Of course, few people "should' be using Family History software in a corporate / work environment :-)
(ps - personally I would even drop IE7 - but I am a lone voice in that so far!)
[kiwi 8 Jul 2010]
Marked as "implemented" as there is now no IE6 specific code in webtrees. We just have to remain vigilant that none creeps in
