Re:Introducing the Firefox debugger.html
by mschuster91 on Thursday September 15, 2016 @02:12AM
(#12503838)
> 2. Ummm...don't you have to test against non-WebKit browsers, anyway?
Testing in Chrome on OS X takes care about Chrome, Windows, Safari, Android, iOS (even though the iOS Webkit has some quirks) and Firefox. Compatibility between browsers in rendering is not an issue these days any more, the only notorious exception being Internet Explorer, but even there the margin is getting smaller and smaller.
I usually develop and full-test in Chrome first, and do a quick "does everything look and behave correctly in other browsers" at the end, so far I have not encountered any major differences between the platforms.
Re:Introducing the Firefox debugger.html
by Sylos on Thursday September 15, 2016 @04:53AM
(#12504436)
Then what's different about this to only developing in Firefox and afterwards testing in the other browser?
Re:Introducing the Firefox debugger.html
by mschuster91 on Thursday September 15, 2016 @08:34AM
(#12505532)
Because Firefox is dog slow (I hope that at least the frequent UI lockups due to synchronous scripts in the site are soon history), and cannot speak with anything webkit.
2. Ummm...don't you have to test against non-WebKit browsers, anyway? Or, do you really expect all of your users to only use WebKit based browsers? That seems problematic.