Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firebug 2.0

blog.getfirebug.com

Post reply on HN
Print view View original

101–110 of 123 posts

Re: Firebug 2.0

#101

Post by frik »

gkoberger wrote: post #16

I use Chrome or Firefox built in developer tools, however I still think Firebug fits my workflow the best. Unfortunately it's too slow to use. The thing I miss the most is the inline display of AJAX call responses, and being able to write/run multi-line snippets of JavaScript (without ctrl+enter). Somewhat interestingly, Firefox built their entire add-on architecture because Joe Hewitt wanted dev tools (for debugging…

Firebug 1.x (only with activated "Scripts" tab) is only slow in newer version of Firefox. http://www.reddit.com/r/firefox/comments/1f4u9x/firebug_make...

I read that Firebug 2 now uses the newer JSDBG2 API of recent Firefox, so there should be no performance problems as there were with Firebug 1.x in recent Firefox versions.

Re: Firebug 2.0

#103

Post by frik »

Firebug 2 finally supports prettified JSON preview of XHR that start "while(1);" and "for(;;);" that is commonly used (also by G+ and FB). Thanks! I prefer Firebug over the other bundled DevTools in FF, Chrome and IE.

@Firebug 2 devs: Please make the JSON preview table-rows-width adjustable - the JSON "key" row-width is too wide!

@Firefox DevTools devs: please finally fix support your JSON preview (see above)

Re: Firebug 2.0

#104

Post by CNojbuHisaVAMCi »

21echoes wrote: post #21
Kiro wrote: post #14

Earlier quoted context omitted.

I find the Firefox dev tools very inferior to Chrome dev tools, missing a lot of "must have" features.

such as? not disagreeing, just wondering what you consider "must have" features that Firefox currently lacks.

Mobile tools, especially user agent spoofing per tab and presets for different devices. And disabling of all caches when the developer tools are open.

Mobile development with Firefox is a pain compared to Chrome.

Re: Firebug 2.0

#105

Post by invmatt »

joewalker wrote: post #46
dfc wrote: post #33

Earlier quoted context omitted.

I hate the fact that the close window/dialog button for the devtools is on the left hand side when every other plugin puts this on the right hand side. I am not an every day user of FF's built in devtools so it is not something that I am accustomed to. Despite firebug's performance troubles when I go to select devtools or firebug I usually opt for firebug simply because the close button drives me nuts.

We moved the button and a number of the tabs in Firefox devtools to be more like the order in Firebug and Chrome devtools. Here's a screenshot from current Nightly: https://i.imgur.com/EmVIZYO.png

New devtools are much improved however would it be possible to remove the dotted lines whilst inspecting an element (toggled option would be fine), just seems to get in the way of things.

Re: Firebug 2.0

#106

Post by stuaxo »

_karthikj wrote: post #93

Not sure why Firefox chose to build their own developer tool when firebug was one of the compelling reason to use firefox and started the trend of having an extensive tool for debugging/inspecting webpages.

I may be wrong .. Originally firebug had to be really slow because of the interfaces available for debugging, the internal tool could work without slowing everything to a crawl.

With the newer debugging interface it seems like firebug can work and the browser can be fast.

Re: Firebug 2.0

#107

Post by iSnow »

andrethegiant wrote: post #8
ep103 wrote: post #2

Still the best developer toolset, on any browser. Unarguably once its combined with FF native tools, and the webdevtoolbar.

I'm always surprised when I read comments about how the Firefox devtools offer the best developer experience. Every single one of these new features (except searching the dom via CSS selectors or regex) have been available in Safari's Web Inspector for OS X for at least a year. Plus, I think the UI is more thought out and easy to use in Safari. Can someone explain what Safari's Web Inspector is lacking?

Even as a Mac user, Safari completely has vanished from my radar. Apple seems too slow to adopt the latest web technologies and Safari to me is a completely lackluster browser. It has neither the market share of IE nor the raw speed of Chrome nor the versatility and configurability of Firefox.

Safari does not work on anything but MacOS and iOS, so developing for it requires additional testing.

Re: Firebug 2.0

#108

Post by rafael-rinaldi »

tambourine_man wrote: post #88
mtrpcic wrote: post #82

Earlier quoted context omitted.

https://github.com/firebug/firebug/tree/master/extension/ski... Look for firebugBig.png and firebugSmall.svg. I _think_ those are the files.

Thanks, but that's not it. Nevermind

Haha trying to talk about .ai and .psd files with programmers is always funny :)

Re: Firebug 2.0

#109

Post by rafael-rinaldi »

orthecreedence wrote: post #40
21echoes wrote: post #21

Earlier quoted context omitted.

such as? not disagreeing, just wondering what you consider "must have" features that Firefox currently lacks.

I've had trouble with them. They don't include inline stack traces for errors, so you have to do a lot more digging to find what happened and where. Also, in the Network panel, every refresh resets your filters so you have to select XHR every time if you don't want to see a bunch of .html/.js file requests (this may have been fixed in FF v30, haven't tested yet). There are just a number of really small issues other t…

Same thing for me. I use Firefox as my main browser and I think it's far better than Chrome, but its native developer tools are just very confusing so I'm sticking with Canary as my development browser.

Re: Firebug 2.0

#110

Post by vitro »

21echoes wrote: post #21
Kiro wrote: post #14

Earlier quoted context omitted.

I find the Firefox dev tools very inferior to Chrome dev tools, missing a lot of "must have" features.

such as? not disagreeing, just wondering what you consider "must have" features that Firefox currently lacks.

One of the features that Chrome has and that is just great is ability to connect resource in the webpage to the resource on your disk. This way, with other tools such as HostAdmin and PerfectPixel you can turn desinged page template into pixel perfect html pretty fast - you just play with the css values in the inspector and your changes write-through to the file on your disk.
Post reply on HN