Open RobinVdBroeck opened 3 years ago
I second this one, considering that loading the current webextension as a temporary addon in Firefox seems to work flawlessy. Having an .xpi installable from firefox store should allow a deeper and widespread testing.
So you did installed it on firefox? Would you mind explaining how you did that?
Sure.
You can temporary install addon on FF directly from source.
I retrieved the unpacked bundle of the extension installing it on chromium e copying it from ~/.config/chromium/Default/Extensions. Surely there's some link on the web where you can download the bundle without needing Chrom* running ,but I dind't investigate
Here's the link
https://clients2.google.com/service/update2/crx?response=redirect&prodversion=50&acceptformat=crx2,crx3&x=id%3Dienfalfjdbdpebioblfackkekamfmbnh%26uc
about:debugging
This Firefox
Load Temporary addon
and select the manifest.json
you find inside the subtree you copied. (For the version I tested it was under ienfalfjdbdpebioblfackkekamfmbnh/1.0.0_0
)The extension will be active until browser reboot, to avoid any potential problem.
@RobinVdBroeck that's something we want to do. Before moving forward, we have a few things on the backlog:
@4javier thank you for sharing steps on installing the extension in Firefox!
Hey all,
as there are only P3 issues open at the moment, is there already a plan / roadmap for the transfer to the Angular monorepo?
@mgechev Please, it would be so helpful if the extension is added to the firefox as-is, without modifications. The current version works okay when added manually via firefox debugging, but it has to be added again and again after closing the browser window.
Angular Dev Tools works very well under firefox 92.0 (excepted the temporary extension problem). However there are at least 2 problems in manifest.json : the properties "version_name" and "background.persistent" are not recognized by Firefox. After fixing the two previous errors and running "web-ext lint" we got 1 error (main.js file is too large) and 8 warnings related to dangerous use of "eval". @4javier Thank you for your help.
I have an environment where all chromium-based browsers are locked down via group policy to prevent any extensions from being installed, but our developers can install Firefox themselves and do what they like with it. So having Firefox support, at least in my group, would be a huge win (apparently no one else in my group knew there was a devtool extension for Angular until now).
Hey everyone, the transfer of angular devtools to the angular/angular repo is under way. It's difficult to share an exact timeline but there will be a lot of effort devoted to it in the next couple of weeks.
Once the transfer is complete, Firefox support will be one of the first things we work on. Thank you all for being patient 🙏
Hey everyone, the transfer of angular devtools to the angular/angular repo is under way. It's difficult to share an exact timeline but there will be a lot of effort devoted to it in the next couple of weeks.
Once the transfer is complete, Firefox support will be one of the first things we work on. Thank you all for being patient 🙏
Thanks. Waiting for this.
To support an open web, the devtools should support Firefox so we can debug our applications in Firefox.