Firefox Developer Edition • Hacker News Board

Re: Firefox Developer Edition

#151

Post by _broody » Mon, Nov 10, 2014, 5:27 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.

Pretty much. I never close Firefox on my laptop, and haven't seen any performance degradation for over a year now.

Chrome on the other side, starts degrading my entire system's performance forcing it to hit swap memory the second the string of tabs on my top bar threatens to stretch across the screen. No need to wait for 'months of use without closing'...

Re: Firefox Developer Edition

#152

Post by nartz » Mon, Nov 10, 2014, 5:31 PM UTC

Firefox already does a lot - how about a website similar to 'RailsCasts' that takes different use cases and shows how to do them with FireFox plugins?

I think its important to differentiate different users / use cases, because 'Web Developer' is pretty broad.

Re: Firefox Developer Edition

#153

Post by Siecje » Mon, Nov 10, 2014, 5:32 PM UTC

tezza wrote: post #130

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…

It'd be nice to have the URL bar entries as combobox dropdowns Hand editing by moving the cursor is so fiddly and error prone. Take: http://my.app/path/to/node?a=123&b=A34 it would be nice to be able to type into the parameters. Say change path to path1 or value of the b parameter from A34 to B67 . Having MRU entries for each param value in a dropdown would be quite useful too.

You can double click 'path' on Window but not on Linux.

https://bugzilla.mozilla.org/show_bug.cgi?id=926249

Re: Firefox Developer Edition

#154

Post by technomancy » Mon, Nov 10, 2014, 5:35 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 would love to have FF profiles as dotfiles that I can actually check into source control and use reliably. I blew a couple hours a few months ago trying to make FF fit into my existing system of dotfiles in git and it was extremely frustrating.

Every other program I use lets me check config into git, but FF insists on storing config data into profiles with randomly-generated names. It's very resistant to automation. I understand there is an FF-specific sync solution, but I want all my config in one place.

Re: Firefox Developer Edition

#155

Post by tdooner » Mon, Nov 10, 2014, 5:40 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…

Cool, thanks for all your hard work on FF dev tools!

One thing I could really use is something that helps me understand how Firefox treats TCP/TLS/SPDY connections. It would illustrate the benefit of using CDN and maybe, with enough instrumentation, would help me tune asset sharding.

I put some thoughts in the uservoice here: https://ffdevtools.uservoice.com/forums/246087-firefox-devel...

Re: Firefox Developer Edition

#156

Post by tjbarbour » Mon, Nov 10, 2014, 5:44 PM UTC

agumonkey wrote: post #19

timdorr wrote: post #9

Here's the prettier link to download: https://www.mozilla.org/en-US/firefox/developer/

I believe this is the stub (~400Ko) Sniffing my laptop gave me this http://download-installer.cdn.mozilla.net/pub/firefox/nightl... Felt weirdly generic since the name didn't indicate any special edition, but I ran it and it says developer edition. ---- tl;dr In case someone needs an offline installer, grab that url.

Thank you, as someone who develops almost exclusively offline, this was crucial ;)

Re: Firefox Developer Edition

#157

Post by acdha » Mon, Nov 10, 2014, 5:45 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…

Critical path performance profiling:

1. Performance timeline which shows major events (e.g. DOMContentLoaded, load event) and the network / scripts which blocked them

2. Initiators for reflow, layout, etc. events. Currently it's really easy to identify a JavaScript hotspot if it's pure JS but it's hard to learn what's triggering hundreds of reflows, particularly in non-obvious cases such as CSS transitions.

Re: Firefox Developer Edition

#158

Post by jwmerrill » Mon, Nov 10, 2014, 5:58 PM UTC

explorigin wrote: post #145

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…

The current debugger lists the current execution stack horizontally. This is bad UI because it's hard to follow. It is more convenient for short stack hops but for deep traversal, it is worse than Chrome's vertical stacking in a tree.

Check the left hand side. There's a tab next to the file list that has a vertical stack trace.

Re: Firefox Developer Edition

#159

Post by Raphael » Mon, Nov 10, 2014, 6:04 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…

Great information here. Please paste your comment here onto the web page for the Developer Edition. I got the impression from the official page that it was just for Web IDE and the dev tools Firefox already had.

Re: Firefox Developer Edition

#160

Post by masklinn » Mon, Nov 10, 2014, 6:07 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…

> What tools do you need?

Safari 8 introduced "breakpoint actions" similar to Xcode's: when a breakpoint is set, it can be configured to not actually break (keep running even if the breakpoint condition matches) and if it matches:

* log a message

* play a sound

* execute code

* run a probe

Each action type can be used any number of time on the same breakpoint.

It's not the most stable and almost undocumented — the only documentation I've found is the second half of WWDC'14 Session 512 "Web Inspector and Modern JavaScript" (starting ~37mn in) — but it's a great system, one I've been waiting for for a long time, and one I'd like to see more of. Especially with all the other features in e.g. the Xcode version: Xcode can ignore the first n hits of a breakpoint and can capture an OpenGL ES frame. In a browser, the breakpoint could allow capturing the DOM state, the renderstate or a WebGL frame.