![]() ![]() Finding line numbers in firebug is very difficult and you can't do it for some content. You get a preview of the images in the resources list and you can actually see which elements are transparent because chrome places the checkerboard behind the image (you do get a preview of the image in firebug but only when hovering over the request node, kind of annoying).Īlso, you can double-click resources and chrome will pop them up in a new tab, VERY nice for when I'm debugging AJAX calls and need to see the formatted exception error in the browser without manually typing in my ajax URLs. The resources tab in dev tools blows the net tab in firebug out of the water. I can quickly click to inspect elements and it expands nodes correctly, taking me to the node I want. I used to have a lot of complaints about Dev tools' elements section but now it seems to operate almost exactly the same as firebug. Turns out I like Dev tools way more than firebug after I got used to it. I realized a little later that Chrome had the same things as Firebug just organized a little differently. I went through and figured out exactly how they were different. It took a bit to adjust and I kept getting confused so I developed a test page on my box and I set them up side by side, firebug on my left monitor and dev tools on my right. ![]() Chrome's developer tools has come a long way over the last year. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |