4 ms·

There are a couple of bugs with IE and older versions of the stock (deprecated) Android browser using flexbox, but I think they're all handled easily enough. Al

There are a couple of bugs with IE and older versions of the stock (deprecated) Android browser using flexbox, but I think they're all handled easily enough. Also, they don't work with IE9 - God forbid you're still supporting that browser.

robin_reala 10y ago
Still supporting IE8, and testing components in IE7. 150k visits last month from IE7, sigh.
- ryanSrich 10y ago
  150k? That's insane. What's the location for those visits? I'm kind of intrigued.
  - robin_reala 10y ago
    Well, that’s out of ~90m visits a month total. This is for GOV.UK, so I suspect most of them are government internal.
    - pbhjpbhj 10y ago
      Do you think Gov.uk should be supporting that 0.25% of users, seems like it's probably a waste of resources. Can't you just settle for graceful degradation? Is there some DDA angle (supporting screenreaders) or other mitigation that's not obvious?
      - robin_reala 10y ago
        It’s not about percentages, it’s about numbers. We don’t actually go out of our way to support it on pages and we don’t tell other departments to test in it, but if you’re building a pattern library it makes sense to do the hard work up front. In terms of graceful degradation, yep. In our current patterns project we’ve dropped all JS for IE7 beyond the HTML5shim. Our support schedule is at https://www.gov.uk/service-manual/technology/designing-for-different-browsers-and-devices https://www.gov.uk/service-manual/technology/designing-for-d...
- squeaky-clean 10y ago
  Like 5% of our traffic comes from IE 6-8.... Thank god for jQuery. And, I can't recall the percentage, but a surprisingly large amount from the stock Android browser (not Chrome, the one that ships on really old phones).
  - noxToken 10y ago
    We have internal support for IE9. Our non-internal traffic for it is almost non-existent. We were getting a small portion of traffic from the stock Android browser as well, but we were finally able to convince them to drop support for it.
- j_r_f 10y ago
  IE8 is bad enough. IE7 sounds like torture.

robin_reala 10y ago

Still supporting IE8, and testing components in IE7. 150k visits last month from IE7, sigh.

ryanSrich 10y ago
150k? That's insane. What's the location for those visits? I'm kind of intrigued.
- robin_reala 10y ago
  Well, that’s out of ~90m visits a month total. This is for GOV.UK, so I suspect most of them are government internal.
  - pbhjpbhj 10y ago
    Do you think Gov.uk should be supporting that 0.25% of users, seems like it's probably a waste of resources. Can't you just settle for graceful degradation? Is there some DDA angle (supporting screenreaders) or other mitigation that's not obvious?
    - robin_reala 10y ago
      It’s not about percentages, it’s about numbers. We don’t actually go out of our way to support it on pages and we don’t tell other departments to test in it, but if you’re building a pattern library it makes sense to do the hard work up front. In terms of graceful degradation, yep. In our current patterns project we’ve dropped all JS for IE7 beyond the HTML5shim. Our support schedule is at https://www.gov.uk/service-manual/technology/designing-for-different-browsers-and-devices https://www.gov.uk/service-manual/technology/designing-for-d...
squeaky-clean 10y ago
Like 5% of our traffic comes from IE 6-8.... Thank god for jQuery. And, I can't recall the percentage, but a surprisingly large amount from the stock Android browser (not Chrome, the one that ships on really old phones).
- noxToken 10y ago
  We have internal support for IE9. Our non-internal traffic for it is almost non-existent. We were getting a small portion of traffic from the stock Android browser as well, but we were finally able to convince them to drop support for it.
j_r_f 10y ago
IE8 is bad enough. IE7 sounds like torture.