Support Firefox

[flying-sheep]

Due to Chrome’s bugginess I prefer developing in Firefox and creating workarounds for Chrome later.

Creating a version of this for Firefox’ dev tools would help me maintaining this workflow.

[zpao]

I'm surprised we didn't have an issue open for this already. We would definitely like to have this but haven't found the time.

[g13n]

I was thinking this issue is related, or it isn't?

[flying-sheep]

me at first too, but read what @zpao said in that bug:

This bug as filed was fixed a while ago and really had nothing to do with React devtools.

that bug was about sourcemaps. we’re talking about a react-devtools addon being available for firefox here

+1 Firefox support is necessary. No more of this "webkit monopoly"

[vipulnsward]

I know a 👍 doesn't help, but 👍 for this 😃 !

[caseyyee]

Just adding another vote here for Firefox :)

[johnmaguire]

👍 I understand Chrome first, and most devs in my office are using Chrome, but there's quite a few of us who still use Firefox, especially since the Dev Edition came out!

[VinSpee]

As a daily Firefox Developer Edition, I'd love to see this

[tushartyagi]

I, too, would love to see the devtools on firefox. I've been using firefox over chrome for quite some time now.

[iamdustan]

Is there any pointers to where any forking would need to take place in the codebase or resources for what it would take to start working in this direction?

[jlongster]

I work on the Firefox devtools team. We don't have great docs for extending the devtools, partially because we hope to improve a few things first. Still, it's not too hard. The hard part is pulling out all Chrome-specific code in the tool.

Ember Inspector did a great job with this. They have an "app" folder here: https://github.com/emberjs/ember-inspector/tree/master/app and it doesn't contain any browser-specific code (it might do browser checks for some things, I don't know). Then they have a folder for the specific browser; here's firefox: https://github.com/emberjs/ember-inspector/tree/master/dist_firefox/lib

That folder contains all the firefox-specific code to install the tool and other things.

Looking through this cool, it looks like it uses Chrome-specific APIs a lot throughout the entire code, which is unfortunate. I don't know how much work it would be to abstract it out.

Can we start a port of these tools for firefox? Is it feasible and viable
to do so?

On Mon, Mar 30, 2015 at 9:59 AM, James Long notifications@github.com
wrote:

I work on the Firefox devtools team. We don't have great docs for
extending the devtools, partially because we hope to improve a few things
first. Still, it's not too hard. The hard part is pulling out all
Chrome-specific code in the tool.

Ember Inspector did a great job with this. They have an "app" folder here:
https://github.com/emberjs/ember-inspector/tree/master/app and it doesn't
contain any browser-specific code (it might do browser checks for some
things, I don't know). Then they have a folder for the specific browser;
here's firefox:
https://github.com/emberjs/ember-inspector/tree/master/dist_firefox/lib

That folder contains all the firefox-specific code to install the tool and
other things.

Looking through this cool, it looks like it uses Chrome-specific APIs a
lot throughout the entire code, which is unfortunate. I don't know how much
work it would be to abstract it out.

—
Reply to this email directly or view it on GitHub
#56 (comment)
.

[MikeRatcliffe]

Facebook already has React Developer Tools, an excellent Chrome extension that could easily be ported to Firefox:

I was thinking that if we detect react on a page that we show a React tab after the markup tab... as to whether this should be baked in with our current toolkit or not, that is another question... that is my preference but @canuckistani would have the final say.

[jeffgca]

@ashneo76 it should be possible to do, other tools have been ported including ember inspector and batarang.

@MikeRatcliffe generally speaking my preference is to not ship framework-related tools in Firefox but instead support them as extensions. If react gets as popular as jquery is it would be more compelling.