From the top of my mind:

1. HTTP Request builder (think cURL with a nicer GUI and the ability to save presets);

2. Web Proxy, able to "stop-and-modify" requests (think Fiddler or Charles);

3. Network conditions simulator for throttling, packet dropping and limited bandwidth, with profiles (e.g. GPRS);

4. Local Mock REST API, with a few predefined endpoints (e.g. /users/) + the ability to create new ones (with configurable values such as random integers between X and Y or a random string which is a valid e-mail);

5. Multi-touch simulator (with a modifier key);

6. A usability test facilitator, able to create test scripts and automatically record timing and extra information (e.g. define a task that ends when user clicks the element with id X; when said user clicks #X, you annotate the time, the number of misclicks, etc). You could also implement this for static images, with clickable regions. I would love you for this one.

Here's the thing that bothers me the most about a lot of the talk about net neutrality by government officials:

> If a consumer requests access to a website or service, and the content is legal, your ISP should not be permitted to block it.

Specifically "and the content is legal" is what raises a flag for me. I've seen similar phrases in nearly everything I've read coming from any government official regarding net neutrality.

If this phrasing makes it into eventual laws regarding net neutrality, it seems to me that it could easily require inspection of all traffic by ISPs to ensure the legality of traffic.

Hi! Just a heads up that folks from the dev tools team will be monitoring this thread and are on-hand to answer questions. We'll try not to thread sit too much. :) In brief, the Developer Edition is a new release channel for Firefox, replacing Aurora (our pre-Beta channel). Everything else about the release cadence is the same.

There are four major new features here:

1. The Firefox Tools Adapter ("Valence"), which lets you use the Firefox dev tools to inspect and debug pages in Chrome for Android and Safari for iOS. The goal: one set of tools to debug any browser.

2. Side-by-side profiles. The Developer Edition defaults to a profile named `dev-edition-default`, which makes it easier to run Developer Edition at the same time as a normal release version of Firefox. You don't have to deal with the profile switcher each time.

3. Developer-friendly defaults. Developer Edition ships with things like remote debugging and browser-chrome debugging enabled by default.

4. And, for all of you who hated Australis, a compact theme with square tabs.

But those are just consequences of the single biggest change:

5. We have a new channel, which new rules. And we want to use it to build the best possible browser for web developers. We can ship new tools that aren't yet ready for the Beta channel, and we can change the browser's appearance and defaults specifically for web developers.

We'll be watching this thread during launch, but you can always submit feature requests on UserVoice. The right people will see them: https://ffdevtools.uservoice.com/forums/246087-firefox-devel...

This isn't a finished product. It's an invitation.

What tools do you need?