It's definitely planned in the future, however probably not until a few months out...

Thanks. Eagerly awaiting.
On 28 Nov 2015 11:52, "Evan You" notifications@github.com wrote:

It's definitely planned in the future, however probably not until a few
months out...

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

I've started work on a firefox version of the same. You can check out my branch hope to finish this in 2-4 weeks.

Progress so far:

@skyronic very cool! Excited to have someone working on this. Let me know if you have any questions :)

Awesome @skyronic , I will check out your branch.

On Mon, 30 Nov 2015 20:19 Evan You notifications@github.com wrote:

@skyronic https://github.com/skyronic very cool! Excited to have
someone working on this. Let me know if you have any questions :)

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

@yyx990803 any news on this?

Almost half a year later. :) Any news?

@yyx990803 , @skyronic - any progress? still awaiting devtools for firefox

throwing in my vote as a firefox developer edition user

Is there any news on this? I'd love to be able to use FF dev edition for Vue just as I do with everything else. @skyronic? Any plans on finishing this or at least releasing some basic instructions to install what you already had?

Thanks!

Hey guys, are you still working in the FF version of dev tools? It would be a great enhancement... Tks!

Yes! I am still working on FF devtools, and I'll be happy with Vue plugin!! :)

Hey folks, can we install a chrome plugin inside firefox? I remember reading this some time back. It was a blog post by Firefox team saying that we can easily install a chrome plugin inside firefox.

Yes, it's called WebExtensions. But I don't think it works with developer tools.

see http://arewewebextensionsyet.com/#devtools.panels

That's bad news.

Still no FF extension?

@yyx990803 You got any update on this topic?

I've 🔔 subscribed this issue for Firefox addon.
Firefox user's life isn't easy with Vue as Chrome. 😭
Still looking forward to using Firefox addon. 😳

// I ❤️ Firefox. Don't tell me to use Chrome.

My christmas wish this year: that there will be a Firefox version of vue-devtools 🎄

I'm interested in this too.

Anyone here wishes to build a firefox addon for Vue? I am open to collaborating, we can build our own version by checking the source code of the chrome version, do let me know if anyone is willing to participate.

Skyronic has started working on it it would seem, maybe try to get in touch?
As for me, my plate is full atm unfortunately.

Hey I had gotten some work done on this a long time ago by re-using ideas from the react-devtools project. I stopped using firefox due to some other reason so I didn't continue work on this.

A lot of the structure for vue-devtools is inspired by https://github.com/facebook/react-devtools

so you'd want to create a folder in 'shells' similar to this one - https://github.com/facebook/react-devtools/tree/master/shells/firefox

The maybe I can start working on your version itself. I've never written a extension, so it will take a little time!

look forward to the firefox version

So, which features are prevent this from just being ported over?

https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Chrome_incompatibilities

I can confirm that this doesn't work for our case: https://addons.mozilla.org/en-US/firefox/addon/chrome-store-foxified/

@gluons Yes, until this is available in normal Firefox we should wait, when it is however, we do not need a new addon in firefox thus, we can close this, what do you think?

Well, that is good news, but I think I will keep this open until the required features land in Firefox stable. In the meanwhile, I'd be happy to take a PR updating the README to point out how to use this extension in Firefox dev build.

I was thinking about a PR, but there are two things holding me back. First I have never contributed to any open source project by means of PR so am not sure about how to do it properly. I can prepare a gist and send it across you @yyx990803 .

But even before that using Chrome Store Foxified requires to sign the extension/addon, for which I had to create an account at AMO. What I am wondering is that for anyone who wants to use vue-devtools in Firefox will need to open an account at AMO just for the purpose of signing the extension.

Wouldn't it be better if we (anyone) can create an accont at AMO and sign the extension and then download the signed extension, which can then be included in this repo as a workaround for Firefox.

Then any subsequent users can just download the signed extension from here and use Install Addon from file to get vue-devtools working in firefox.

I am trying to figure out if such a signed extension can be reused.

@neeravp There is no rocket science in submitting a PR, you just fork the project, edit the README.md file and submit it as a PR, based on the time @yyx990803 or other collaborators have, they'll merge it.

I agree with you and I was going to say this earlier, we can just upload a signed version of the addon rather than have everyone create a firefox account as it is a waste of time and resources, if you are willing, I'd send my addon to you, just try to install it on your firefox dev, and if that's fine, we can upload it directly on github itself.

If you are fine with an unofficial build and want to run VueJS DevTools without the hassle of singing and converting the addon, I made one here.

I posted a lot of info related to Firefox addons on this issue in case you need the info.

I just picked the built version in shells/chrome, duplicated that into shells/firefox and used the web-ext tool and packed it. It is working for me. It would be trivial to ship that to AMO. It would be cool if the original author did it.

Do you guys have problems with the Vue devtools panel not being scrollable? Because I have to close all the tree branches to be able to see anything that is in the lower part of the panels, for example in the Vuex Store panel. This is in Firefox ofc.

I am using Waterfox. I installed vuejs devtool, and restarted browser. However I couldn't find Vue tab in inspect window.

We're still waiting on Firefox to complete bug 1300590 such that $0 and inspect bindings will work in the devtools.inspectedWindow.eval API. Once that lands this is the list of things I believe need to be done for this issue to be closed out.

• Add the extra slash to the file:///* match pattern #339 : update the manifest.json permissions
• Updated the Roboto woff2 file with new hinting #340 : Investigate custom fonts that aren't working in Firefox
• Firefox WebExtension support #341 : Turn on support for Firefox
  • Change enabled popup text to say "Open DevTools"
  • Add <meta charset="utf-8"> to the popups and the devtools-background.html
  • Need to review the webpack options for target browser and dev mode I think we could likely just add { firefox: 55 }
  • Update manifest description to mention Firefox as well as Chrome
• Submit WebExtension to AMO
• Update README to refer to new Firefox extension and workaround for versions older than Firefox 55
• Remove Firefox workaround doc in a follow up PR when Firefox ships WebExtension API to release (Fx 55)

Investigate custom fonts that aren't working in Firefox

I'm getting this error:

downloadable font: GSUB: too large substitute

And it looks like this stackoverflow answer might be the path forward: https://stackoverflow.com/a/36803177/897414

Looks like the issue was reported Dogfalo/materialize#4493 and fixed here Dogfalo/materialize@5f8b46c I'll have a look at updating the font files.

Need to review the webpack options for target browser and dev mode I think we could likely just add { firefox: 55 }

Getting an error with 55 right now. Chrome is currently shipping 58 and 60 for Canary so I don't think it'll be an issue to use Fx 48 for now.

Here's the error:

Module build failed: Error: Support data exists for the following versions of firefox: 43, 44, 45, 46, 47, 48. Please raise an issue at https://gitlab.com/Rich-Harris/buble/issue

Bug 1300590 - Implement support for $0 and inspect bindings in devtools.inspectedWindow.eval just landed. It will probably be available in the next Nightly update :D

Great! Hope this plan come true soon

This is now official, but how exactly I install it on Firefox ?
Do I still need this workaround ?
I someone working on an official Firefox addon ?
This is very exciting!

@lionel-bijaoui

Firefox continues its rapid implementation of new WebExtension APIs. These APIs are designed to work cross-browser, and will be the only APIs available to add-ons when Firefox 57 launches this November.

It's on Firefox 57? It may not work now. I think we still need it for now.

@gluons Oh... I read it to fast it seem... I will wait then... 😞

@lionel-bijaoui Firefox Nightly is 56 now. So close. Let's try it when 57 come. 😜

@lionel-bijaoui having a workaround is silly when you can have a one click install I really hope the VueJS DevTools devs spent a few minutes to provide an official unlisted addon untill it will be ready to be listed on AMO. It makes no sense to wait for v57 especially since some of us use v56 already.

Installing Vue-devtools via the workaround (https://github.com/vuejs/vue-devtools/blob/master/docs/workaround-for-firefox.md) works great on Firefox 54 (released just a few days ago).

Only thing I noticed is that I can't scroll inside the devtools window.

@andreicristianpetcu THANK YOU! It work perfectly (except for the scroll)

@Hendriksie what is the advantage of the workaround over the one click install I proposed? The workaround seems complicated and unnecessary but please correct me if I'm wrong. I tend to like thing that just work.

Either is fine. Using Chrome Store Foxified directly just cuts out a middleman :)

Based on @clarkbw's comment above, it looks like all the pieces are in place for this, we just need to get it submitted to AMO and wait for the next release of Firefox to pick up a few fixes on our end.

Something appeared in AMO 👻

Firefox workaround doc was removed in c8b9b1e and README was updated in 182fe68

I think we're all done here!

Thanks to everyone who helped and especially @yyx990803

@yyx990803 Can you add Vue logo on AMO page? Maybe easier to recognize.