Live data from Hacker News

Future of Firefox DevTools

paulrouget.com

31–40 of 170 posts

Re: Future of Firefox DevTools

#31
post #8

Earlier quoted context omitted.

It opens a new buffer, than can be saved as an existing file.

Give me this now. (ps - awesome work and communication!)

You might be interested in checking out Brackets (http://brackets.io/) which has some live development capabilities for CSS at least right now. I believe it only works with Chrome though, currently.

Re: Future of Firefox DevTools

#32
post #24

I've recently changed back over to Mozilla, this just proves that it was the correct decision.

I'm not quite sure if a mockup proves anything, unless you mean the part about them asking the community.

Re: Future of Firefox DevTools

#33

Earlier quoted context omitted.

Haha, I just switched from Chrome to Firefox because I hate how Chrome prioritizes Google Search over my previous history. It's idiotic. Here, let me show you a clear example. http://i.imgur.com/uNsh7Yv.png Firefox clearly has the superior bar.

You can deactive this in chrome://settings/. I did it after your post. I find it also annoying.

What setting do you change?

Re: Future of Firefox DevTools

#34
One small thing that I haven't seen yet (in FF or Chrome) is a feature where I could get the IP address that was used to retrieve a given resource in the network tab. This would be hugely helpful when dealing with sites that are backed by more than one server. Also, ability to reset DNS cache (BTW, DNS cache seems to be shared between private and regular browsing modes).

The ability to lock onto a specific IP for a given domain would be pretty kick-ass too. Not a replacement for /etc/hosts, but just choosing one of the 2 IP's for example.com, etc.

Another nice feature would be to get the network tab to ignore resources loaded from external domains, only show external resources, or show both. Maybe even more fine grained with/without subdomains.

Re: Future of Firefox DevTools

#35
I find the responses here really strange, has anyone here actually used the devtools in pratice? The firefox devtools seem to me just a awful waste of time from the beginning, they are years behind the competition and the development progress is so slow that I've given up on them. I'm using firefox as my main browser but for web development (dom/css inspection, javascript debugging) there is currently nothing that beats the chrome devtools.

Re: Future of Firefox DevTools

#36
post #15

The right-hand-side docking looks absolutely amazing ( http://i.imgur.com/duQOXq7.png ). I have another bit of feedback. The web console has three positions available: Above, Below, and Window. With Firebug, I like to have the console open in another monitor and give the browser viewport maximum screen real estate in front of me. Firefox's web console doesn't let me do this because in "Window" mode it doesn't quite a…

Fixed in Firefox 21.

My apologies, I remember in the original post you asked us to hold off on providing feedback unless the issues were present in recent Firefox versions. On the plus side, this motivated me to switch to Firefox Aurora just now and I must say, I'm extremely impressed!

Re: Future of Firefox DevTools

#37
How many devs actually use Firefox's dev tools? I see all of that praise "looks awesome, looks amazing, etc" But do people really use those amazing things? I just find the Chrome dev tools orders of magnitude more usable than Firefox's. It's mostly a large amount of what you could call details but it makes all the difference. It all flows better, reduces the amount of thinking you have to do as well as the number of clicks and keypresses. I think Mozilla should start by fixing all of these little problems before jumping into huge stuff like they seem to like to do with the cli, python library etc.

Re: Future of Firefox DevTools

#39
post #35

I find the responses here really strange, has anyone here actually used the devtools in pratice? The firefox devtools seem to me just a awful waste of time from the beginning, they are years behind the competition and the development progress is so slow that I've given up on them. I'm using firefox as my main browser but for web development (dom/css inspection, javascript debugging) there is currently nothing that be…

> there is currently nothing that beats the chrome devtools.

That's the point of this post. It's that pretty soon, Firefox is going to have much improved devtools. They include some features that interest us greatly.

Re: Future of Firefox DevTools

#40
Are there any plans to implement an instrumenting profiler in addition to the existing one? Not having call count is a huge minus for me. Devtools has a sampling profiler like Chrome (which also doesnt provide call counts). So the only instrumenting profilers remaining for JS on Windows are Firebug and an outdated, abandoned version of Safari :(
Post reply on HN