7 ms·

Just a little reminder: > Let me just list some of the stuff IE9 doesn't support: * Application Cache (offline) * Web Workers (threads in JavaScript) * HTML

Just a little reminder: > Let me just list some of the stuff IE9 doesn't support: * Application Cache (offline) * Web Workers (threads in JavaScript) * HTML5 Forms (validation mechanism, CSS3 selectors) * JavaScript Strict Mode * ForeignObject (embed external content in SVG) * SMIL Animations (SVG animations) * File API * WebGL (3D) * CSS3 Transitions (for animations) * CSS3 Text Shadow * CSS3 Gradients * CSS3 Border Image * CSS3 Flex box model * ClassList APIs * FormData * HTML5 History API * Drag'n Drop from Desktop ... > Let me list stuff that IE9 can do others don't: * text-overflow doesn't work in Firefox 4. * Calc is not supported in Chrome 9. > So that's why I don't consider IE9 a Modern Browser. Source: http://people.mozilla.com/~prouget/ie9/ http://people.mozilla.com/~prouget/ie9/

kin 16y ago
it drives me nuts that I still have to write IE specific CSS.
- tomjen3 16y ago
  You don't have to, you just need to find a market with better users (or go into the mobile sphere, where there are really only two browsers). Or give up on the idea that everybody has to see you page in exactly the same way - as long as it works and isn't totally broken, who cares?
  - dspillett 16y ago
    Exactly. When I'm doing something that I'd like to be pixel perfect (or have a clever layout by some other measure) my current priories are: 1. works perfectly as intended in Firefox and Chrome at reasonable window sizes (this usually means it should in other reasonably compliant browsers too) 2. degrades gracefully (i.e. some display discrepancies but no behavioural problems or illogical on-screen layout that inhibit viewing/use of the content) in other browsers (including IE8), and/or when pressed into a very small viewport (such as on a mobile device, though obviously some content is never going to be particularly usable at QVGA resolutions) 3. try not to do anything that will break the design on IE6, but no care overly if that does happen (and give users a warning that it might at the top of each page: the one IE specific CSS hack I use is one to make that message display to IE6 users)
  - kin 16y ago
    True, most of the time I really don't have to worry about IE. Occasionally, though, I'll have a job with 40%+ IE visitors. Those times, I really have to make things look right, and it's always something hacky.
- jasonkester 16y ago
  Does it also drive you nuts that you have to write FF-specific CSS and Chrome-specific CSS. If not, why not? There are still lots of browsers out there, and they all work in slightly different ways. It's been this way since Netscape came out and was different from Mosaic. It'll continue to be this way until one browser dominates to the point where others go away. Personally, I'm rooting for Chrome. Like you, I get tired of having to cross-tweak my code. But realistically I find I spend more of my time these days working around FF issues than IE ones.
- est 16y ago
  Stop write -o -moz -webkit in yours, too.
- mediacrisis 16y ago
  Its becoming a pretty common practice to charge extra for IE6 support. If you hate IE that much its always an option to charge for the full gamut, but don't act surprised when the phone stops ringing as much ;) On a serious note, IE has always been a challenge for front end dev, but its at least up front about its lack of support. Chrome, FF and Safari will sometimes have a minor margin bug that will drive me more insane then the expected behavior of IE.
gim-matt 16y ago
Are any of those things an actual standards? There is plenty of CSS that you need to write specifically for Chrome and Firefox.
- acabal 16y ago
  Yeah, but... not even text-shadow and gradients? Come on, IE :(
  - paul9290 16y ago
    I was hoping the text on my site was going to look proper in IE9. What the heck is this? Anyone here from MS care to explain why they continue to hold back the web and make us front end engineers work harder? Uggghh...
    - rbanffy 16y ago
      > Anyone here from MS care to explain why they continue to hold back the web I am not from MS, but I can explain. Most of their money comes, directly and indirectly, from selling Windows and Office licenses. Making the web functional enough that it would compete with desktop apps would lessen their lock-in and reduce their future revenue. IE has been, since its very first release, designed to fragment the web and to prevent it from becoming a viable applications platform. It and its matching development tools are designed to lure companies into writing IE-specific code, locking themselves into Microsoft ecosystem. That's why they are having difficulties getting rid of IE 6 and XP - it worked too well. I am sure you were expecting their PR spin on this ;-) I am curious about what would it be.
      - encoderer 16y ago
        This argument has always baffled me. First, don't attribute to malice what could better be explained by incompetence. Second, isn't Ajax the most fundamental usability feature that allows web apps to compete with desktop apps? And who created the XMLHttpRequest object? Exactly.
    - 16y ago
catch23 16y ago
too bad it doesn't support css3 gradients -- hopefully the IE6 gradient hacks will still work.
- carey 16y ago
  As far as I can tell (http://blogs.msdn.com/b/ie/archive/2010/08/17/ie9-opacity-and-alpha.aspx http://blogs.msdn.com/b/ie/archive/2010/08/17/ie9-opacity-an... for example), IE9 in IE9 standards mode supports neither filters nor VML. I hope I’m not too optimistic in thinking that its SVG support should be good enough to use that as a workaround.
  - duopixel 16y ago
    They are using it for their own gradients: background-image: url(http://www.beautyoftheweb.com/assets/images/layout/glass-pane.svg http://www.beautyoftheweb.com/assets/images/layout/glass-pan...); Awkward workaround.
  - pero 16y ago
    Last I checked (6 months ago), cufon was broken due to VML. EDIT: Fixed cufon-side, probably the day after I last checked. Oops.
kawohi 16y ago
Exactly. I don't see how many people can be excited about IE9. No CSS3 Transitions? Come on thats my FAVORITE part of CSS3!
- barista 16y ago
  and that's a very convincing reason to support it in a browser
  - tomelders 16y ago
    UI feedback is very important to a well rounded user experience. CSS3 transitions will be a big part of UI design in the future. Just how far off that future is... I'm guessing around IE11, maybe IE12.
ZeroGravitas 16y ago
Is spell checking in IE9 now, or is this feature that's been standard in other browsers for about 5 years now not considered cool enough to even mention its glaring absence from IE in this (admittedly non-comprehensive) list?
- bgrainger 16y ago
  It does not have a spell checker. The Microsoft Connect issue for this (with 40+ duplicate suggestions) that's closed as "By Design" is: https://connect.microsoft.com/IE/feedback/details/598257/spellchecker https://connect.microsoft.com/IE/feedback/details/598257/spe...

kin 16y ago

it drives me nuts that I still have to write IE specific CSS.

tomjen3 16y ago
You don't have to, you just need to find a market with better users (or go into the mobile sphere, where there are really only two browsers). Or give up on the idea that everybody has to see you page in exactly the same way - as long as it works and isn't totally broken, who cares?
- dspillett 16y ago
  Exactly. When I'm doing something that I'd like to be pixel perfect (or have a clever layout by some other measure) my current priories are: 1. works perfectly as intended in Firefox and Chrome at reasonable window sizes (this usually means it should in other reasonably compliant browsers too) 2. degrades gracefully (i.e. some display discrepancies but no behavioural problems or illogical on-screen layout that inhibit viewing/use of the content) in other browsers (including IE8), and/or when pressed into a very small viewport (such as on a mobile device, though obviously some content is never going to be particularly usable at QVGA resolutions) 3. try not to do anything that will break the design on IE6, but no care overly if that does happen (and give users a warning that it might at the top of each page: the one IE specific CSS hack I use is one to make that message display to IE6 users)
- kin 16y ago
  True, most of the time I really don't have to worry about IE. Occasionally, though, I'll have a job with 40%+ IE visitors. Those times, I really have to make things look right, and it's always something hacky.
jasonkester 16y ago
Does it also drive you nuts that you have to write FF-specific CSS and Chrome-specific CSS. If not, why not? There are still lots of browsers out there, and they all work in slightly different ways. It's been this way since Netscape came out and was different from Mosaic. It'll continue to be this way until one browser dominates to the point where others go away. Personally, I'm rooting for Chrome. Like you, I get tired of having to cross-tweak my code. But realistically I find I spend more of my time these days working around FF issues than IE ones.
est 16y ago
Stop write -o -moz -webkit in yours, too.
mediacrisis 16y ago
Its becoming a pretty common practice to charge extra for IE6 support. If you hate IE that much its always an option to charge for the full gamut, but don't act surprised when the phone stops ringing as much ;) On a serious note, IE has always been a challenge for front end dev, but its at least up front about its lack of support. Chrome, FF and Safari will sometimes have a minor margin bug that will drive me more insane then the expected behavior of IE.

gim-matt 16y ago

Are any of those things an actual standards? There is plenty of CSS that you need to write specifically for Chrome and Firefox.

acabal 16y ago
Yeah, but... not even text-shadow and gradients? Come on, IE :(
- paul9290 16y ago
  I was hoping the text on my site was going to look proper in IE9. What the heck is this? Anyone here from MS care to explain why they continue to hold back the web and make us front end engineers work harder? Uggghh...
  - rbanffy 16y ago
    > Anyone here from MS care to explain why they continue to hold back the web I am not from MS, but I can explain. Most of their money comes, directly and indirectly, from selling Windows and Office licenses. Making the web functional enough that it would compete with desktop apps would lessen their lock-in and reduce their future revenue. IE has been, since its very first release, designed to fragment the web and to prevent it from becoming a viable applications platform. It and its matching development tools are designed to lure companies into writing IE-specific code, locking themselves into Microsoft ecosystem. That's why they are having difficulties getting rid of IE 6 and XP - it worked too well. I am sure you were expecting their PR spin on this ;-) I am curious about what would it be.
    - encoderer 16y ago
      This argument has always baffled me. First, don't attribute to malice what could better be explained by incompetence. Second, isn't Ajax the most fundamental usability feature that allows web apps to compete with desktop apps? And who created the XMLHttpRequest object? Exactly.
  - 16y ago

catch23 16y ago

too bad it doesn't support css3 gradients -- hopefully the IE6 gradient hacks will still work.

carey 16y ago
As far as I can tell (http://blogs.msdn.com/b/ie/archive/2010/08/17/ie9-opacity-and-alpha.aspx http://blogs.msdn.com/b/ie/archive/2010/08/17/ie9-opacity-an... for example), IE9 in IE9 standards mode supports neither filters nor VML. I hope I’m not too optimistic in thinking that its SVG support should be good enough to use that as a workaround.
- duopixel 16y ago
  They are using it for their own gradients: background-image: url(http://www.beautyoftheweb.com/assets/images/layout/glass-pane.svg http://www.beautyoftheweb.com/assets/images/layout/glass-pan...); Awkward workaround.
- pero 16y ago
  Last I checked (6 months ago), cufon was broken due to VML. EDIT: Fixed cufon-side, probably the day after I last checked. Oops.

kawohi 16y ago

Exactly. I don't see how many people can be excited about IE9. No CSS3 Transitions? Come on thats my FAVORITE part of CSS3!

barista 16y ago
and that's a very convincing reason to support it in a browser
- tomelders 16y ago
  UI feedback is very important to a well rounded user experience. CSS3 transitions will be a big part of UI design in the future. Just how far off that future is... I'm guessing around IE11, maybe IE12.

ZeroGravitas 16y ago

Is spell checking in IE9 now, or is this feature that's been standard in other browsers for about 5 years now not considered cool enough to even mention its glaring absence from IE in this (admittedly non-comprehensive) list?

bgrainger 16y ago
It does not have a spell checker. The Microsoft Connect issue for this (with 40+ duplicate suggestions) that's closed as "By Design" is: https://connect.microsoft.com/IE/feedback/details/598257/spellchecker https://connect.microsoft.com/IE/feedback/details/598257/spe...