Re:The IE CSS Bug Which Cost Me A Month’s Salary
by jhancock on Friday October 23, 2009 @01:45PM
(#899239)
The excuse for not testing on all browsers is that its incredibly time consuming. It also requires you to be at your main workstation that has all those test VMs.
[ Parent
| on HN ]
Re:The IE CSS Bug Which Cost Me A Month’s Salary
by thaumaturgy on Friday October 23, 2009 @01:58PM
(#899270)
I will take this opportunity to keep plugging for http://crossbrowsertesting.com/
I'm not affiliated with them in any way, they've just made my one of my jobs much easier for not much money, and they hang out on HN sometimes besides.
Re:The IE CSS Bug Which Cost Me A Month’s Salary
by tonetheman on Thursday October 29, 2009 @08:38PM
(#911263)
Not sure if you have tried the new bookmarklet we released, but it changes the way you interact with the service. In two clicks (click on the bookmarklet, click on the browser / platform you want to test in), the page you are currently viewing is launched in the remote configuration and the browser is opened to your current page. It really improves the work flow. You can read more about it at http://crossbrowsertesting.com/blog/new-cool-bookmarklet.
Appreciate the plug! Tony Founder - CrossBrowserTesting.com
Re:The IE CSS Bug Which Cost Me A Month’s Salary
by systemtrigger on Friday October 23, 2009 @04:56PM
(#899606)
Others: Adobe BrowserLab and LitmusApp. BrowserLab is fast and free. LitmusApp is much slower and costs us $49/month but it has some advantages - it has a good series processing UI, it links to w3c html and css validation results, and it doesn't crop the bottom of the page.