6 ms·

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

by kin 16y ago

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.

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

by kin 16y ago

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

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.