My company has just decided to start browser testing in IE 8, Chrome (Win), and Safari 3.0 (Win). Was curious to hear from fellow Web Developers, how much extra time on average (percentage wise) do you think we should be allotting for building CSS/XHTML for our Emerging Browsers? Additionally, curious how easy these browsers are to create for, ranging from IE 5 (DEATH) to Firefox 3.0 (sweet).
Hi, How do you mean? You would just tell the problems to them or you would also solve them? If only problems, they will probably use browsershots.org and not your service... If solving the problems... an easy 10-20$ per browser? Maybe less if it's easy to solve... but in IE6 most things aren't easy so 10-20$ than Greetz
It doesn't take any more time to test in all of the big four browser engines. When working, I have my editor open, plus Firefox and Opera (Linux), and IE and Safari (Vista in a VM). After any change to the structure or presentation, alt+tab rotates through the browsers, and a ctl+r or f5 refreshes. IE8 is a testing/beta version. One does not test one's html/css against a beta version; you test the beta version against expected behavior and file a bug if it screws up. You might take a glance at secondary browsers for a given rendering engine, e.g. Chrome for Webkit (Safari), a whole potload for Gecko (Firefox), Opera and games for Presto (Opera), and Avant, etc. for Trident (IE). You do not code for a browser. You write semantic, well structured and valid html plus css for compliant UAs of all brands. Only IE presents real issues, but if you begin on a solid foundation, it's not that big a deal to make IE happy too. cheers, gary