News for hackers. Stuff that matters.
Re:Announcing WebKit2 by aaronbrethorst on Thursday April 08, 2010 @11:40PM (#1251798)
It's not just you. FF on Mac's only redeeming quality is Firebug. Pity the WebKit inspection/debugging tools are so awful still.
Re:Announcing WebKit2 by tcdent on Friday April 09, 2010 @02:56AM (#1252093)
I've find the debug tools in the WebKit nightlies to be more polished and just as capable as those offered in Firebug, without the jank of Firefox on the Mac. What specific features are essential to your workflow that WebKit doesn't offer?
Re:Announcing WebKit2 by idm on Friday April 09, 2010 @10:40AM (#1252787)
I hate to repeat it, but it's really true. Firebug makes it so easy to debug CSS due to the saneness of the CSS UI. WebKit's inspector UI is a nightmare for tracing a CSS calculation.
Re:Announcing WebKit2 by pavs on Friday April 09, 2010 @01:49PM (#1253318)
I wouldn't call it a nightmare, its just not as good as firebug yet but made major improvements over the last year or so. If there was no firebug today than I Web Inspector would be the second best choice. Their CSS editing and tracing needs to be a bit more intuitive, not a fan of clicking check boxes to remove CSS element.
Re:Announcing WebKit2 by cubicle67 on Friday April 09, 2010 @02:54AM (#1252090)
Perhaps my requirements are much less demanding than yours, but I find the Safari develop tools to be more than adequate. Quite like them, in fact. Which aspects were you finding to be awful?
Re:Announcing WebKit2 by lukifer on Friday April 09, 2010 @04:32AM (#1252219)
I wouldn't call them awful; they only seem that way in comparison to the awesomeness that is FireBug.