Skip to content
This repository has been archived by the owner on Feb 13, 2019. It is now read-only.

The Windows XP problem #44

Open
zachleat opened this issue Feb 27, 2012 · 5 comments
Open

The Windows XP problem #44

zachleat opened this issue Feb 27, 2012 · 5 comments

Comments

@zachleat
Copy link

Should the API even show Internet Explorer as an option to visitors that are using Windows XP with features that require IE9+?

@nimbupani
Copy link
Member

I suppose we could do that, also for Firefox 3.6 on Mac users who use Tiger or below? I am not sure where to draw the line tho :/

@addyosmani
Copy link

Perhaps we should take a second look at the support/recommendation matrix we're assuming and flesh that out a little.

For IE/XP, I agree that it doesn't really make sense to show IE9+ if it requires a complete OS-upgrade, or perhaps we do show it but add a note/icon related to the OS needed.

I guess this also relates back to whether or not we should consider #47 (Chrome Frame) for oldIE (which is relevant if IE9 isn't being shown).

@jonathantneal
Copy link
Member

There is no realistic chance Windows XP users will ever see IE9 because Microsoft made a deliberate decision to use Direct2D APIs which are not available in that legacy operating system.

Microsoft Windows XP Internet Explorer users are in a unique position that requires a financial commitment on their part to update their web browser.

I'm unsure if it would be bias of us to tell IE users to switch browsers rather than follow the upgrade path Microsoft has requested of them. Or, is it in the users best interest to provide for them the shortest path to success?

@addyosmani
Copy link

I would say it would be in their best interests to suggest the shortest path to success, but..others may disagree :)

@zachleat
Copy link
Author

+1 for shortest path.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants