4 ms·
Chrome comes with the element inspector built in which replicates a lot of the functionality of Firebug.
by amandle 17y ago
Chrome comes with the element inspector built in which replicates a lot of the functionality of Firebug.
- markkanof 17y agoThe element inspector is handy, but personally I would also need JavaScript step through debugging like Firebug provides.
- tlrobinson 17y agoHave 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.
- mhansen 17y agoChrome has step through debugging. Check the 'Scripts' tab of the inspector
- ddemchuk 17y agoThe 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
- tlrobinson 17y agoAre you sure? I think you can edit the text of stylesheets, and add new style properties on individual elements too.
- ddemchuk 17y agounless 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 :-)
- Huppie 17y agoThough 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.
- mhansen 17y agoEditing 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.
- Confusion 17y agoA 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.