Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox Developer Edition

developer.mozilla.org

Post reply on HN
Print view View original

181–190 of 300 posts

Re: Firefox Developer Edition

#181

Post by masklinn »

sp332 wrote: post #42
Gracana wrote: post #31

I noticed there's a checkbox for "make FirefoxDeveloperEdition my default browser," is that just a vestigial thing from the regular FF installer, or is it actually safe for me to use FFDE as my regular browser?

This page says "We'll include experimental tools that aren't yet ready to ride the trains to release." But https://hacks.mozilla.org/2014/11/mozilla-introduces-the-fir... says "It’s a stable developer browser which is not only a powerful authoring tool but also robust enough for everyday browsing." So maybe the browser part is stable, but the tools are experimental? And it uses a different profile by default, so a br…

From other comments, it's ~aurora (pre-beta) but it may get new tools from nightly much sooner, very soon after nightly and long before they move to beta.

So the browser itself should be pretty stable, but the devtools may not be.

It may also gets developer-specific UI customisations which never get merged into the beta/release channels.

Re: Firefox Developer Edition

#182

Post by gpo »

dschep wrote: post #88

Will https://launchpad.net/~ubuntu-mozilla-daily/+archive/ubuntu/... switch to this new build or will there be a new PPA for Firefox Developer Edition?

Yes! (I automagically got firefox dev from that PPA)

Re: Firefox Developer Edition

#183

Post by asantos3 »

rpwverheij wrote: post #167

Just downloaded it and gave it a try. I've been using chrome for development for a long time and I must say this looks really good and I'd really like to switch cause I like the firefox image/mission much more. However I'm experiencing some problems editing my .less files directly from the browser. They don't show up in the list of style sheet files, even though I have "show original sources" checked. Where do I subm…

Bugzilla? https://bugzilla.mozilla.org/

Re: Firefox Developer Edition

#184

Post by Yoric »

stephen wrote: post #134
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…

> 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. That's amazing. I can't wait until we have standard wire protocols for all of this so that I can stay in an IDE while writing GWT/Coffeescript/JS/etc., e.g.: https://github.com/sdbg/sdbg (AFAICT both the FF and Chrome…

Well, the code is better than that of Communicator :)

Re: Firefox Developer Edition

#185

Post by [deleted] »

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…

[deleted]

Re: Firefox Developer Edition

#186

Post by Yoric »

kgtm wrote: post #118
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…

Firefox is unusable for developers with poor eyesight that use OS-level accessibility features such as high contrast on recent versions of Windows. There is an open bug but no love: [ https://bugzilla.mozilla.org/show_bug.cgi?id=790706 ]. Firefox forces high-contrast colors, completely destroying HTML rendering, with no option to disable this behavior. Using a high contrast theme in Windows doesn't mean i don't want…

I am not familiar with this part of the code, but generally, the answer to this question is « lack of manpower, but if you volunteer to implement it, we'll be glad to help you out and have you onboard. »

If anybody motivated to help us implement features reads these lines, the next step is to join us on IRC: irc.mozilla.org, channel #introduction .

Re: Firefox Developer Edition

#187

Post by Yoric »

acqq wrote: post #150
callahad wrote: post #90

Earlier quoted context omitted.

The release process might help explain it: https://wiki.mozilla.org/RapidRelease or, if you're familiar with Chrome's stable / beta / dev / canary channels, it's largely the same model. As far as fundamental web platform features are concerned, the Developer Edition is a normal pre-Beta channel. It's primarily that more willing to promote new tooling up from Nightly into the DevEdition or to set different default pre…

I see, the "new rules" are easiest to summarize as one more "let's do it like Chrome" step.

No, that's not the "new rules", that's the "rules that have been in place forever, but if you are familiar with Chrome, these are the same." The new rules is that Developer Edition takes place of Aurora in that scheme.

Re: Firefox Developer Edition

#188

Post by Yoric »

realusername wrote: post #82

I'm taking advantage of the fact that there's a few Mozilla developers around to say a big thank you to the team. I've never used most of the features of the developer edition except the console and everything is great on this developer edition. I'm a proud owner of a Firefox OS phone and the simulator is really good and fast, I think I'm going to make an app or two during my spare time ! A big thank you to all the t…

I'm not part of the devtools team, but I'm going to shamelessly accept the thank you on their behalf.

Have fun coding :)

Re: Firefox Developer Edition

#189

Post by Yoric »

px1999 wrote: post #115

The developer tools are the only thing stopping me from switching back to FF from Chrome. The tooling in Firefox does seem to be improving rapidly (kudos to the devs for that, I'm not trying to trivialise the hard work that they've been putting in, by any means), but there are still several basic(?) features missing from the script debugger. Calling this a "developer edition" is IMO a misnomer until you can reasonabl…

This is largely the codebase that used to be Aurora. However, it's not a "nicer packaging", it's a complete change of direction for Aurora.

Now regarding your needs, the devtools teams is watching this thread, but just in case they miss your message, you might be better off making your requirements known here: https://ffdevtools.uservoice.com/

Re: Firefox Developer Edition

#190

Post by acqq »

Yoric wrote: post #187
acqq wrote: post #150

Earlier quoted context omitted.

I see, the "new rules" are easiest to summarize as one more "let's do it like Chrome" step.

No, that's not the "new rules", that's the "rules that have been in place forever, but if you are familiar with Chrome, these are the same." The new rules is that Developer Edition takes place of Aurora in that scheme.

Your "in place forever" conflicts with the comment to which I have asked for an explanation what the new rules are:

callahad:

"5. We have a new channel, which new rules." (sic)

Note that the Developer Edition is definitely new (1), and callahad also explains in his reply where it is positioned:

"As far as fundamental web platform features are concerned, the Developer Edition is a normal pre-Beta channel. It's primarily that more willing to promote new tooling up from Nightly into the DevEdition or to set different default preferences, for instance."

1) https://hacks.mozilla.org/2014/11/mozilla-introduces-the-fir...

Post reply on HN