News for hackers. Stuff that matters.
Re:IE9 has been released by patrickaljord on Tuesday March 15, 2011 @12:58AM (#2326048)
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/

Re:IE9 has been released by ZeroGravitas on Tuesday March 15, 2011 @08:08AM (#2327059)
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?
Re:IE9 has been released by bgrainger on Tuesday March 15, 2011 @08:57AM (#2327206)
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/spe...
Re:IE9 has been released by kin on Tuesday March 15, 2011 @01:02AM (#2326063)
it drives me nuts that I still have to write IE specific CSS.
Re:IE9 has been released by tomjen3 on Tuesday March 15, 2011 @04:24AM (#2326555)
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?

Re:IE9 has been released by dspillett on Tuesday March 15, 2011 @07:30AM (#2326939)
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)

Re:IE9 has been released by kin on Tuesday March 15, 2011 @02:21PM (#2328719)
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.
Re:IE9 has been released by jasonkester on Tuesday March 15, 2011 @08:08AM (#2327060)
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.

Re:IE9 has been released by mediacrisis on Tuesday March 15, 2011 @12:13PM (#2328112)
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.

Re:IE9 has been released by est on Tuesday March 15, 2011 @08:42AM (#2327165)
Stop write -o -moz -webkit in yours, too.
Re:IE9 has been released by gim-matt on Tuesday March 15, 2011 @01:12AM (#2326088)
Are any of those things an actual standards? There is plenty of CSS that you need to write specifically for Chrome and Firefox.
Re:IE9 has been released by bad_user on Tuesday March 15, 2011 @02:03AM (#2326234)
The standard is defined by what browsers implement. Thus Microsoft is keeping the standard back.

That's OK, consider Javascript Web Workers; apps will be able to run without direct support, but on capable browsers will get a performance boost. That's fine by me, more reasons for people to upgrade from IExplorer.

Re:IE9 has been released by acabal on Tuesday March 15, 2011 @01:34AM (#2326161)
Yeah, but... not even text-shadow and gradients? Come on, IE :(
Re:IE9 has been released by paul9290 on Tuesday March 15, 2011 @05:42AM (#2326692)
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...

Re:IE9 has been released by rbanffy on Tuesday March 15, 2011 @06:50AM (#2326822)
> 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.

Re:IE9 has been released by encoderer on Tuesday March 15, 2011 @05:48PM (#2329566)
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.

Re:IE9 has been released by jasonlotito on Tuesday March 15, 2011 @09:35AM (#2327359)
> Anyone here from MS care to explain why they continue to hold back the web and make us front end engineers work harder?

Web sockets. Consider for a moment the issue with web sockets, and how the implementation was wrong, despite being put into browsers. Browsers had support for web sockets, and developers were developing for it. That obviously changed rather quickly.

Microsoft's idea is not to support things before they are relatively stable and supportable. Basically, their idea is if they put something into IE9, they aren't removing support.

That doesn't mean they aren't working on new features, nor are they preventing developers from adding it to their version of IE9 to test out the technologies. They call this "Site Ready". Basically, they feel the technology is ready for end users.

Now, I'm merely providing the information they are providing to developers. Do not argue with me.

Re:IE9 has been released by emehrkay on Tuesday March 15, 2011 @09:03AM (#2327238)
It pains me that I have to hack for IE f'n 9 -- their best browser to date.

Text-shadow and gradients would move design ahead in a good way. At least there are hacks, ms-filter cruft for text shadow and svg for gradients

Re:IE9 has been released by rimantas on Tuesday March 15, 2011 @03:38AM (#2326467)

  Are any of those things an actual standards?
Well, depends how do you define "actual standards". But pretty much yes, there is an big effort to have this consistent across browsers. Links to some:

  > * Application Cache (offline)
http://www.w3.org/TR/offline-webapps/

  > * Web Workers (threads in JavaScript)
http://www.w3.org/TR/workers/

  > * HTML5 Forms (validation mechanism, CSS3 selectors)
http://www.w3.org/TR/html5/association-of-controls-and-forms...

  > * File API
http://www.w3.org/TR/FileAPI/

  > * WebGL (3D)
http://www.khronos.org/registry/webgl/specs/latest/

  > * CSS3 Transitions (for animations)
http://www.w3.org/TR/css3-transitions/

  > * CSS3 Text Shadow
http://www.w3.org/TR/css3-text/#text-shadow

  > * CSS3 Gradients
http://www.w3.org/TR/css3-images/#gradients

  > * CSS3 Border Image
http://www.w3.org/TR/css3-background/#border-images

  > * CSS3 Flex box model
http://www.w3.org/TR/css3-flexbox/

  > * ClassList APIs
http://www.w3.org/TR/html5/common-dom-interfaces.html#common...

  > * FormData
http://www.w3.org/TR/XMLHttpRequest2/#the-formdata-interface

  > * HTML5 History API
http://www.w3.org/TR/html5/history.html#the-history-interfac...

  > * Drag'n Drop from Desktop
http://www.w3.org/TR/html5/dnd.html#dnd
Re:IE9 has been released by recoiledsnake on Tuesday March 15, 2011 @10:37AM (#2327631)
IE9 HTML Labs site for experimental features.

http://html5labs.interoperabilitybridges.com/

Re:IE9 has been released by kawohi on Tuesday March 15, 2011 @01:41AM (#2326179)
Exactly. I don't see how many people can be excited about IE9. No CSS3 Transitions? Come on thats my FAVORITE part of CSS3!
Re:IE9 has been released by barista on Tuesday March 15, 2011 @01:54AM (#2326211)
and that's a very convincing reason to support it in a browser
Re:IE9 has been released by tomelders on Tuesday March 15, 2011 @05:57AM (#2326721)
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.
Re:IE9 has been released by catch23 on Tuesday March 15, 2011 @01:15AM (#2326101)
too bad it doesn't support css3 gradients -- hopefully the IE6 gradient hacks will still work.
Re:IE9 has been released by carey on Tuesday March 15, 2011 @01:35AM (#2326163)
As far as I can tell (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.
Re:IE9 has been released by duopixel on Tuesday March 15, 2011 @02:08AM (#2326250)
They are using it for their own gradients:

background-image: url(http://www.beautyoftheweb.com/assets/images/layout/glass-pan...);

Awkward workaround.

Re:IE9 has been released by pero on Tuesday March 15, 2011 @02:42AM (#2326332)
Last I checked (6 months ago), cufon was broken due to VML.

EDIT: Fixed cufon-side, probably the day after I last checked. Oops.