Even with frameworks like GWT you end up scratching your head because of IE6 specific problems.
How much discount you would give if you do not have to support IE6? Or how much of the overall time is spent on IE6 issues?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Even with frameworks like GWT you end up scratching your head because of IE6 specific problems.
How much discount you would give if you do not have to support IE6? Or how much of the overall time is spent on IE6 issues?
Well, as an example from a recent project I worked on (and the IE6 wrangling came down to me) the total project cost was supposed to include getting the site working in IE6. Then it turns out the client had a very complex design layout.
In the end, we probably spent 7 man-weeks solely on making sure the site worked perfectly in IE6 (and was near pixel-perfect which the client demanded as well). IE7 required approximately an hour or so for some tweaks. Every other relevant browser (FF 2+, Chrome, Safari 3+, Opera 9.6+) rendered and acted correctly immediately without any tweaks required.
We have now changed our standard contract to explicitly exclude pixel-perfect IE6 rendering, unless the client wishes us to quote separately. At that point we can see the design before saying how much it’ll cost.