Slashdot Mirror


Google Kills Apps Support For Internet Explorer 8

An anonymous reader writes "Google today [Friday] announced it is discontinuing support for Internet Explorer 8 in Google Apps, including its Business, Education, and Government editions. The kill date is November 15, 2012. After that, IE8 users accessing Google Apps will see a message recommending that they upgrade their browser."

3 of 296 comments (clear)

  1. Another nail for XP by juventasone · · Score: 5, Informative

    The summary leaves out the interesting part: IE8 is the latest version available for Windows XP. And there's no place that XP exists more than business, education, and government. This is Google's way to get sysadmins comfortable with Chrome in the workplace.

    1. Re:Another nail for XP by viperidaenz · · Score: 4, Informative

      Businesses don't tend to use the OS install that comes with the machine, they load their own builds they have made and tested themselves.

      Support = security fixes.Come 11 April 2014, no more security fixes for XP. Good luck getting Office 2014* that will install on XP as well.

      * or 2015, 2016, 2017....

  2. Re:It's well deserved. by KingMotley · · Score: 4, Informative

    Off the top of my head:
    Opacity (real opacity, including opacity on PNGs with an alpha channel).
    Being able to define colors using RGBA
    CSS3 transforms
    Fully supporting @font-face for real web fonts
    HTML5 video support with H.264/MPEG4 so we can drop flash video players finally
    WOFF font support instead of the EOT (IE-only font format)
    Box shadows
    multiple backgrounds on a single object
    CSS3 selectors (:last-child, :nth-child, etc)

    Stuff even IE9 doesn't support:
    text-shadows
    3d transforms
    aync on script tags
    web sockets
    Filereader API (Smarter upload buttons)
    CSS3 transitions
    CSS3 gradients
    HTML5 form elements (date picker, range, integer, etc)

    Yes, those are all things that we use on our web site, or wanted to use and either had to write custom fallbacks just for IE, rewrite to use a different (more difficult, less efficient, larger) technique, or just let IE look like crap.