Firefox debuts new developer toolbar
blog.mozilla.org
blog.mozilla.org
There still seems to be some sort of memory leakage though. I have to shut down the browser every so often to clear out the 3GB of ram it suddenly decided it needed to have.
I think I'm actually quite sensitive to that, but haven't felt about Chrome that way yet. Could you explain what features you mean in particular?
(People of course disagree on which of those are bad and which are good.)
And I'm talking about barebones Chrome. Sometimes using extensions or activating/deactivating some flags can hinder/improve the performance.
The only thing that keeps me here, is the extensions not available on Safari (my other favorite webkit browser).
But overall it seems more slow on launch (even on clean install).
I find I use both regularly, and which I use by default changes often, depending on the circumstance. E.g. they're both pretty fast these days, but on different things. FF seems more memory efficient overall, but chrome's per-tab-process thing makes it easier to manually reclaim memory by closing a tab (the per-tab-process also probably makes chrome less able to share memory between tabs, so there seems an inherent tradeoff, and explains FF's win here).
So it seems a virtuous cycle, and chrome's to be lauded not only for a great browser, but for heating up the browser race in a way that seems to have resulted in every browser improving.
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/lates...
There are 18a2 builds in there, I'm using it now! However, I haven't seen it mentioned on the main aurora release page, so proceed with caution.
The amount of flash I use on a daily basis is so incredibly minimal these days. I've started using the built in plugin blocking with firefox. The only time I really turn it on is for Netflix and the occasional video that isn't part of the HTML5 beta on youtube is about it.
( not that any of this is an excuse to not fix the bug :P )
Also, it is extremely valuable to have these tools on every browser I happen to use. I can see what's wrong with my website--or anybody's website--at any computer. If you go to some page and something doesn't work, I can just open the developer tools on your browser and try to sort it out.
So while most people don't need these tools most of the time, they can still be useful once in a while and have a negligible cost.
Lets assume a full 25% is dev tools (I think its likely to be much less), so 4.25Mb per user. That's 1418Tb, or just under 500 3Tb disks. Considering that's spread across 350 million users, I think that's not too much at all, and its probably much less.
[1]https://wiki.mozilla.org/images/e/ed/Analyst_report_Q1_2010.... [2]http://www.mozilla.org/en-US/firefox/all.html
I'd be more worried about memory consumption, wasted CPU cycles, lost opportunities to let the CPU sleep, the cost of running CI tests...
I am also worried about the increase in the attack surface exposed to random pages downloaded from the Web.
Also, having the tools built in means that they are tested every time any core Firefox code is changed leading to a much more stable environment.
a) It's better to have it baked into the browser in general, if it's something you use. Worse if it's not, though.
b) Screenshots with selectors are pretty awesome, and I don't think most extensions would provide that
Also I've not seen a screenshot tool that allowed an id to be specified before as someone said this will/does.
Allows you to capture a defined region or the entire page, and upload / edit it online.
Tying this down to the specific domain of web development will probably help its longevity though.
I'm very excited about the add-your-own feature and hope it's similar.
Anyone have any idea on how to change the shortcut? No luck in about:config.
alt-T W v
which looks a little unwieldy, except you don't have to move from the home keys, and I find it much easier to type than
hands up, look for fn, left middle to shift and left index to fn, right middle float up and over to f2
You can muscle memory a short menubar keyboard sequence pretty quickly if you use it enough.
Of course that doesn't help you, but this has annoyed me on mac, and I think they deserve the blame ;)
Looks good though.
Sticking with Firebug until this feature is added.
As it stands, using Firefox on Linux (Openbox) feels like a huge step back from Chrome.
That said, there are a couple of other things that keep me on Chrome such as its element inspector.
Lately they haven't stopped releasing new great things: Persona, lljs, WebPlatform (co-participation), now this developer command bar, ... sth else? Impressive.