screenshots!

android 4, pretty good	android 2.3, shockingly still works	iOS 3, still using an original iPhone? good luck.
IE7 pretty bad	IE8 slightly off	Windows Phone 8.1, no worries here

.
Notes:

• IE8 has issues when trying to select a language.
• We shouldn't be serving JS to dinosaurs like IE7 or even Android 2.3 or iOS 3.
• More detailed feature detection should be used to determine who gets the JS and who doesn't.

CSS wise there are some spacing issues between the search input and search button on older androids,
IE7 doesn't look right at all, but that should be served without JS.

The biggest challenge I see on this front is implementing some sort of feature detection to serve JS to the devices
that support the features we use.

Hi @Jdrewniak, I have a card (T124827) in the Analysis project that will help to address the issue of how much the older browsers are used.

Hopefully, there isn't a majority of use on those older browsers and with the upcoming analysis, we can effectively block JS from going to them.

Change 269673 had a related patch set uploaded (by Jdrewniak):
Improving cross-browser CSS - Adding autoprefixer - fixing a templating bug in typehead

https://gerrit.wikimedia.org/r/269673

Just so everyone doesn't have to click through browserstack like I did:

IE6, let's be real here...	IE 7, CSS ok, no JS	IE 8, works
iOS 3, works	Android 2.3, works	Windows Phone 8.1 ,works
Safari 5, works	Firefox 10, works	Opera 12, works

thanks, @Jdrewniak - the IE6 doesn't look quite as bad as I had expected ;)

It seems that the recent changes (due to UI standards) have broken styling a little. We should check all these devices again.

Change 269673 merged by jenkins-bot:
Improving cross-browser CSS - Adding autoprefixer - fixing a templating bug in typehead - disabling javascript in IE6

https://gerrit.wikimedia.org/r/269673