4 ms·
Nah ... that's about right, I've been doing html/css for almost 9 years and hard core javascript/ui stuff for another 4 or so. Almost without fail, fixing stuf
by trustfundbaby 15y ago
Nah ... that's about right, I've been doing html/css for almost 9 years and hard core javascript/ui stuff for another 4 or so.
Almost without fail, fixing stuff for IE takes as long as it does to just build the feature in the first place (so 4 hours to do a layout then another 3 or 4 to get it working properly in IE), with CSS/html layout that number has dropped as IE6 has been phased out, but I find that its actually moved over into doing js stuff in IE8 and 7.
- gscott 15y agoThe solution may be to design your site and test in Internet Explorer before even looking at it in any other browser. It might be faster for you to resolve the quirks in FireFox & Chrome then IE. Reversing your process might speed up your development time by 20%.
- Isofarro 15y agoNo, that introduces the same type of bias, just from the opposite direction. The key is to keep a broad range of browsers quickly on hand to regularly check _while_ you develop. There's no reason not to have multiple browsers quickly available - modern computers have sufficient processing power to run multiple applications simultaneously these days.
- paul9290 15y agohow do you fix ie7 and 8 css issues? Do you use hacks? That's what I have been doing but would like to get away from this as some employers frown on it.
- bartonfink 15y agoCan't you surround your CSS includes with conditional comments to load ie-specific stylesheets? I'm not a web-designer by any stretch, but I thought that was the usual way to work around IE-specific quirks.
- paul9290 15y agoUNfortunately that still takes time and possibly more time then using css hacks, which are quick and dirty.