blueveek

You can use the `cookie` tool in what's called the "command line". It's been there for quite a while now: https://hacks.mozilla.org/2012/08/new-firefox-command-line-h...

Granted, it's not an actual panel in the toolbox, but it gets the job done.

Sure, but that's only in index.xul, which is a very small part of the project. Everything else is plain old js+html (xhtml necessary for localization). Apologies, I didn't notice that when I said "there's no XUL in there".

As a meta-discussion, <vbox> is just a fancy way of saying:

div { display: -moz-box; -moz-box-orient: vertical; }

...which is the old flexbox implementation. But I digress :)

edit: link to the MDN article about `display: box`: https://developer.mozilla.org/en-US/docs/Web/CSS/box-orient

There is no XUL in there.

> Is this itself entirely a webapp?

Actually, yes: http://dxr.mozilla.org/mozilla-central/source/browser/devtoo...

7 bytes: !''|2+2

:)

Brendan chose to leave, because it was hurting Mozilla. This is not a "corporate decision".

They didn't step down because of Brendan, but for different reasons.

"The three board members ended their terms last week for a variety of reasons. Two had been planning to leave for some time, one since January and one explicitly at the end of the CEO search, regardless of the person selected."

[0] http://arstechnica.com/business/2014/03/three-mozilla-board-...

"All he had to do was lie".

Are you suggesting this would've been better, in the grand scheme of things?

> With this editor, after you make the changes, do you have to copy-paste that back into your source to save it?

Currently yes. However, we have plans to make this better soon. (we call them Project Maps, and they're on the roadmap)

Smooth 60 fps for me on Firefox 26, OS X (stats say at 1250x702 resolution).

Promises and generators actually work magnificently well together. I would recomend taking a look at an implementation of Task.js [1] [2] and, for example, some of its (increasing) usage across the Mozilla codebase [3].

[1] https://github.com/mozilla/mozilla-central/blob/master/toolk...

[2] https://developer.mozilla.org/en-US/docs/Mozilla/JavaScript_...

[3] http://dxr.mozilla.org/mozilla-central/search?tree=mozilla-c...

These comparisons bring up memories of when we used to benchmark empty for loops. I think today’s microbenchmarks are starting to feel just like that.

Comparing the execution time of a hundred thousand (sync or not) callbacks vs. a hundred thousand (sync or not) promises is, in many cases, not a good or deciding factor for what tool you should pick from the toolbox. I would assert that in realistic scenarios, it really doesn't matter.

If you don't know already, a huge UI overhaul is planned to land sometimes between Firefox 25 or 26 [0]. As far as I know, better performance is a big reason for the change as well.

[0] https://people.mozilla.com/~shorlander/ux-presentation/ux-pr...

Tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=901365

edit: seems to be already fixed in ESR 17.0.7