Firefox Developer Edition • Hacker News Board

Re: Firefox Developer Edition

#231

Post by nailer » Mon, Nov 10, 2014, 11:27 PM UTC

callahad wrote: post #43

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 le…

I want to control / inspect Internet Explorer and Chrome desktop and Firefox in one consistent app. Moving between different devtools sucks. Browserstack and VMs have horrible latency.

It would be cool for Developer Edition to help me test websites everywhere. I'm not sure how technically you would do that though.

Re: Firefox Developer Edition

#232

Post by kolme » Mon, Nov 10, 2014, 11:47 PM UTC

I have a few problems with this.

First, using a browser which includes fancy experimental features might result in the page looking or behaving differently in the users' (stable) browsers. I see this as kind of risky, that's why I usually develop against stable browsers and use the nightly/aurora for personal browsing.

Second, having browser-chrome debugging on by default is not very helpful for web developers, it actually gets in the way. It might be more useful to activate these features in the nightly channel, where people are more actively debugging the browser itself.

Third, if this channel is the intended one for developers, why ship the development tools with the stable release?

Re: Firefox Developer Edition

#233

Post by pbhjpbhj » Mon, Nov 10, 2014, 11:55 PM UTC

acdha wrote: post #133

warcode wrote: post #52

Will this version survive months of usage with multiple open tabs without performance deteriorating massively like the regular firefox? I left FF after my 10th profile reset / reinstall to get back to "normal" performance.

This is almost certainly caused by an extension. If you use Firefox with few or no extensions (e.g. 1Password doesn't cause problems) you'll find this doesn't happen.

Or just cruft from an old profile. A year or two back I had to start with a fresh profile and found FF ran far-far better.

Re: Firefox Developer Edition

#234

Post by mbrubeck » Mon, Nov 10, 2014, 11:56 PM UTC

acqq wrote: post #228

mbrubeck wrote: post #222

Earlier quoted context omitted.

We've done that frequently with the Aurora channel too, so in terms of release management rules, it's just a new name and focus for an existing channel.

Does it mean Developer Edition == Aurora + different default settings + additional tools? Or, what are the exact differences between Aurora and Developer Edition?

Yeah, pretty much. "Developer Edition" is the new name for the Aurora channel. There is no more "Aurora."

(Well, almost. The "Developer Edition" stuff is desktop-only for now, so the alpha-branch builds for Android are still branded as "Aurora." But Aurora for Andoid and Dev. Edition for desktop are built from the exact same source code.)

Re: Firefox Developer Edition

#235

Post by kristopolous » Tue, Nov 11, 2014, 12:10 AM UTC

I'm going to complain that it doesn't work on my tiling window manager. Usually I can't do this because I'm not the target audience.

But this time I am!!! So yeah, menu doesn't work in notion. There you go!

Re: Firefox Developer Edition

#236

Post by nubbie » Tue, Nov 11, 2014, 12:39 AM UTC

cturhan wrote: post #215

As it is developer edition, would you give us option to enable/disable CORS policy.

Trying Firefox again after many years on Chrome. As a developer, this is the thing I'm missing most so far.

Have been using the Allow-Control-Allow-Origin: * extension[1] on Chrome, while not perfect, is tolerable.

1. https://chrome.google.com/webstore/detail/allow-control-allo...

Re: Firefox Developer Edition

#237

Post by geoka9 » Tue, Nov 11, 2014, 1:40 AM UTC

oib wrote: post #125

paulojreis wrote: post #61

Earlier quoted context omitted.

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 configu…

The second one is possible with the Tamper Data plugin: https://addons.mozilla.org/nl/firefox/addon/tamper-data/

It would be very handy to be able to modify the payload of requests/responses as well without resorting to MITM proxy applications.

Re: Firefox Developer Edition

#238

Post by gsam » Tue, Nov 11, 2014, 1:41 AM UTC

cturhan wrote: post #215

As it is developer edition, would you give us option to enable/disable CORS policy.

I agree, although obviously it needs to be smart about how widely it disables. There was an addon available but it got removed from addons.mozilla.org I assume because it violated security. The developer still hosts the addon though.

Re: Firefox Developer Edition

#239

Post by gsam » Tue, Nov 11, 2014, 1:46 AM UTC

Looking forward to see how much of a 'Web IDE' can actually be achieved. I continually feel like I should be making things in the browser, but there's no adequate editor still.

Re: Firefox Developer Edition

#240

Post by geoka9 » Tue, Nov 11, 2014, 1:46 AM UTC

paulojreis wrote: post #61

callahad wrote: post #43

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 le…

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 configu…

Very nice list. I would also add the ability to associate breakpoints with DOM elements. As in "break on any attempt to read/modify a given element". That would be extremely helpful in debugging the hodge-podge of Javascript libraries that many modern web pages are.