Hacker News Reader

Comment by ddemchuk | Hacker News Reader

Does not anyone else get really let down every time they read a Chrome submission that doesn't announce that Firebug has been ported over?

I've started using Chrome for my day to day browsing, but I'll never be able to wholeheartedly switch until Firebug arrives.

View on HN

Chrome comes with the element inspector built in which replicates a lot of the functionality of Firebug.

The element inspector is handy, but personally I would also need JavaScript step through debugging like Firebug provides.

Have you actually tried WebKit's developer tools lately?

It has a great DOM inspector (allows editing), network/script/rendering timeline, step-through debugger, profiler, cookie and local database inspector, and Chrome even has a heap analysis tool (see which objects are allocated).

It's far better than Firebug, at least for JavaScript developers, IMO.

Chrome has step through debugging. Check the 'Scripts' tab of the inspector

The element inspector comes somewhat close, but you can't add css attributes to selectors, only modify existing ones, which really makes the thing useless when doing front end dev

Are you sure? I think you can edit the text of stylesheets, and add new style properties on individual elements too.

unless you're seeing something I'm not seeing, you can only modify existing attributes. If you could show me though, an upvote will be in your future :-)

Though not as useful as firebug you are able to add a 'style="<custom css>"' attribute to an element by hovering over and clicking the '?=""' that appears.

Editing the text of stylesheets: no.

Editing style rules applied to elements: yes, you can do this. Select an element in the inspector, and you can click to edit its style rules.

A lot, but not enough. In place editing of HTML, CSS and cookie manipulation are almost non-existent, especially compared to the way firebug allows it.

Reply on news.ycombinator.com