61–70 of 79 posts
Chrome is my daily browser. Web inspector is quite good and it does the job most of the time. The JS console is awesome. But for some reason, doing anything else but using that JS console never feels quite as good as doing it within Firebug.
Earlier quoted context omitted.
There is no equivalent to the Firefox JavaScript console, especially when you add the jQuery plugin to it. Chrome console sucks. Their DOM explorer is superior in some ways, though.
> There is no equivalent to the Firefox JavaScript console [...] Chrome console sucks. So there is indeed an equivalent, which you don't like for reasons you refuse to explain. I am disappoint.
Agreed, I'm genuinely interested to know what I'm missing out on! :)
1. Refactor a ton of code (this is not much fun, as you're just breaking things and fixing new bugs)
2. Add support for lots of other browsers (this is also not much fun, see #1)
3. Try exciting new off-the-wall ideas (awesome!)
How many people are going to continue to contribute when #1 and #2 drag on from weeks to months to years of discussions about correct refactoring methodologies and Doing It Right This Time? How far will the other browser's development tools come in this time?
Perhaps #3 will save the project, but I sadly predict the eventual demise of a giant.
Earlier quoted context omitted.
The Firebug team is worried because Mozilla have been passive-aggressively antagonistic towards them for a long time. Mozilla heavily promoted their abjectly useless "Web Developer Toolbar" extension for years, even bundling it with the browser by default. They also have not been shy about breaking Firebug with every major release, basically not taking it seriously at all. Now they've started down the usual embrace-e…
Mozilla heavily promoted their abjectly useless "Web Developer Toolbar" extension for years, even bundling it with the browser by default. The Web Developer Toolbar was made by Chris Pederick, not Mozilla. It’s also never been bundled with Firefox.
Obnoxiously hard to google for, I ended up having to dig up a Windows VM and an old Firefox installer to figure out what it was.
I would love to see a JavaScript debugger that could break to something like an ipython shell. It's the one thing I really miss moving from server side to client side debugging.
how is that different from a firebug/webkit inspector javascript console if you don't mind me asking? I'm not really familiar with ipython.
Earlier quoted context omitted.
Mozilla heavily promoted their abjectly useless "Web Developer Toolbar" extension for years, even bundling it with the browser by default. The Web Developer Toolbar was made by Chris Pederick, not Mozilla. It’s also never been bundled with Firefox.
You're right, the orthogonally-useless https://addons.mozilla.org/en-US/firefox/addon/6622/ is what I was remembering, it was bundled vaguely as "Developer Tools" in the installer until Firefox 3. Obnoxiously hard to google for, I ended up having to dig up a Windows VM and an old Firefox installer to figure out what it was.
Earlier quoted context omitted.
> Why? What difference do you see between the browsers debugging-wise? Feature-wise, very little. But as I said - I do find I can work faster with Firebug - I much prefer the the DOM inspector (one click node editing, css editing, the fact that it live updates the DOM as it is changed via any JS running on the page) and the console (DOM/JS object inspection and having XHR logging in the console itself and not on anot…
> one click node editing Yes the Webkit DOM inspector lacks that. > css editing It does have that on the other hand. > the fact that it live updates the DOM as it is changed via any JS running on the page My DOM inspector does seem to do that as well, though it doesn't highlight the altered subtrees the way Firebug does. > DOM/JS object inspection Has been in for a long time, though it could be missing some bells and…
I know, but CSS editing is easier with Firebug.
> My DOM inspector does seem to do that as well, though it doesn't highlight the altered subtrees the way Firebug does.
Not nearly the in same way a Firebug does it, I find it very useful for the amount of DOM manipulation I do with JS.
> Has been in for a long time, though it could be missing some bells and whistles.
Again it's the "bells and whistles" that really make the difference for me some of the time. The less time it takes me to debug something, the better.
That said, I still use Chrome inspector on a daily basis, there's no fanboyism from my part.
Earlier quoted context omitted.
> but firebug blows chrome's debugger out of the water. Could you please describes the ways in which it "blows chrome's debugger" [actually the Webkit Development Tools, it's been much more than a debugger for quite a long time) "out of the water" in your opinion?
One wonderful thing about Firebug: When editing a CSS property, pressing UP and DOWN will iterate through all of the possible values of that property. For example, editing "display: none", you can quickly find out what values "display: " can take. I really miss that in the chrome debugger :(
Earlier quoted context omitted.
> but firebug blows chrome's debugger out of the water. Could you please describes the ways in which it "blows chrome's debugger" [actually the Webkit Development Tools, it's been much more than a debugger for quite a long time) "out of the water" in your opinion?
One thing that I always go back to Firebug is for the 'Persist' mode on the Network tab. In case your server side code is redirecting to some other page or site (payments etc) you need to see what was passed to the server and what redirection loops is it going through etc. Another thing that I haven't found Chrome to be able to do is show me events in the DOM tree (I admit I need FireQuery to do that). That really he…
Safari's version has that, not sure about Chrome.
In the DOM inspector, right pane (the one starting with the Styles group), scroll to the bottom and you might find a group called "Event Listener".
You can even switch between viewing only the events bound specifically on the currently-selected node, or those bound on all its ancestors as well (to visualize the bubbling sequence).
Earlier quoted context omitted.
I've pretty happily switched to Chrome, which seems to do everything I used to ask Firebug to do. Although honestly I no longer use Firebug because I no longer use Firefox, and I no longer use Firefox because it takes up an obscene amount of vertical real estate compared to Chrome.
This is true, but ironically Chrome's dev tools take up more vertical space than Firebug. I'm happy I've made the switch, though it would be nice if Chrome/webkit traded some flashy icons for a more space efficient table especially in the "Resources" tab.