Live data from Hacker News

Firefox Developer Edition

developer.mozilla.org

191–200 of 300 posts

Re: Firefox Developer Edition

#191

Earlier quoted context omitted.

I swear this type of comment is becoming like a meme, it's pretty much repeated on every HN thread about Firefox. The response is standard too... Electrolysis. Wait for it. https://wiki.mozilla.org/Electrolysis/Roadmap

I'm kind of hoping that Eloctrolysis never becomes main-line. Right now I have a browser that isolates misbehaving web pages (Chrome) and a browser that allows me to have a million open tabs simultaneously (Firefox). If I could only choose one I'd choose the browser that isolates misbehaving web pages but both is even better.

Chrome doesn't isolate misbehaving webpages. The pages are grouped together under a few parent processes. The more pages you have open, the larger the group and a page crash will take out many more pages at the same time.

Originally the idea was for every page to be isolated but that didn't scale so well.

Re: Firefox Developer Edition

#192
post #135
post #102

Earlier quoted context omitted.

You know you can do this with the CSS inspector in Chrome, without any extension, right?

How?

Haven't used it in a while, but IIRC in the Sources tab of Chrome's Dev Tools, right-clicking a directory brings up a context menu with an "Add folder to workspace" option, which has you pick a local directory to map to the source directory. Then if you edit a file in the dev tools and command-S, it'll save that file where it appears in the local directory you picked.

Re: Firefox Developer Edition

#193
post #192
post #135

Earlier quoted context omitted.

How?

Haven't used it in a while, but IIRC in the Sources tab of Chrome's Dev Tools, right-clicking a directory brings up a context menu with an "Add folder to workspace" option, which has you pick a local directory to map to the source directory. Then if you edit a file in the dev tools and command-S, it'll save that file where it appears in the local directory you picked.

Not just that, I recently found out that it also auto-saves changes that you make right in the css panel of the DOM inspector. It backs up your original value by commenting it out, but be aware of this when you experiment with this! Fiddling in with css in the inspector will make it persistent!

Re: Firefox Developer Edition

#194
Why the black theme? I think that as developers/designers we should use environments which closely resemble that of the users we're creating for. Colors influence people's emotions, as well as how they perceive a specific design. Even if you are a designer, you're still a user; a user of your own creations. And when you change the mindset to that of a user, why not change the environment as well?

(just a thought)

Re: Firefox Developer Edition

#195
For those who like me are wary of running unverified binaries:

- checksums: https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/late...

- signatures: https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/late...

- signing key: https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/lat...

edit: reformatting

2nd edit: added https

Re: Firefox Developer Edition

#196

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…

Drag and drop nodes in the Inspector like Chrome does.

Re: Firefox Developer Edition

#197

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 really like to switch to this to get away from Chrome but there is one thing stopping me. Which is that in Chrome when I'm debugging JS I can see a full list of files in their folders and can open them up to see them and add breakpoints and things. Like this http://derp.co.uk/1ae64 But in Firefox all I get is http://derp.co.uk/3be04 which is of zero use to me and it means I can't use it over Chrome. Am I miss…

It does work for me, though: http://i.imgur.com/Hj6IlvM.png

Re: Firefox Developer Edition

#198

For those who like me are wary of running unverified binaries: - checksums: https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/late... - signatures: https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/late... - signing key: https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/lat... edit: reformatting 2nd edit: added https

You're wary of running unverified binaries but you're OK when they're verified by a checksum downloaded over unencrypted HTTP?

Re: Firefox Developer Edition

#199

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…

I see that concerning point one and two there is option 'edit and resend' visible if you hover over request in network tab, and there is also option 'enable persistent logs', that shows what happens between refreshes. Don't know how it works, just playing around for 10 minutes. Overall I'm impressed with new network panel, much better than before.

That's pretty excited. Unfortunately when I try to edit and send a POST it gets changed to an option. Anyone know why?

Re: Firefox Developer Edition

#200

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…

I wonder if this implementation will allow the GWT debugger to work with Firefox again. The last version of FF that works with it is, I think, 26. When they removed the NPAPI layer.
Post reply on HN