browser-wakatime
browser-wakatime copied to clipboard
wakatime
Firefox Support Plz
WebExtensions APIs are pretty similar to chrome and a little bit tweaking should be sufficient to make firefoxers happy.
Pull request #75 will need to be merged to have proper support. That said, it will be up to @alanhamlett to upload an official addon to the Mozilla addons site.
@kovetskiy Still waiting on @alanhamlett to build and upload an official addon to the Mozilla addons site.
I'm wanting to fix some bugs, implementing domain-based rules for smarter tracking, and a few other features in the Chrome extension. Then we'll release both Chrome and Firefox plugins.
is there any ETA and/or roadmap?
On Sun, Jun 23, 2019, 17:41 Alan Hamlett [email protected] wrote:
I'm wanting to get the Chrome version out of beta first (Chrome's version shouldn't even be 1.0 yet since it's still beta). That means fixing some bugs, implementing domain-based rules for smarter tracking, and a few other features. Then we'll release both Chrome and Firefox plugins with a 1.0 version.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/wakatime/chrome-wakatime/issues/49?email_source=notifications&email_token=ACAN7ZBTC4MTS4MSIDYH7KLP36DQTA5CNFSM4CUWFTDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYLABTY#issuecomment-504758479, or mute the thread https://github.com/notifications/unsubscribe-auth/ACAN7ZBXV6NQL7KVCNUBW53P36DQTANCNFSM4CUWFTDA .
any ETA and/or roadmap?
No, unfortunately it's not on our roadmap yet since we haven't scoped out the work. It's just on our backlog with no ETA. I can say it's next on the list after the Desktop app.
Guys i feel like we should have a Firefox extension. I mean you have this page but you click on it and you get "It's not ready". Come to find out it isn't even in the works?
I mean, the work is mostly done. I've got a build of it that works. @alanhamlett just needs to actually publish it and do some cleanup.
My development time is mostly on Firefox. It's a waste of time guessing missing time records. It's too long waiting for the plugin.
@alanhamlett While the codebase supports Firefox, you have yet to publish the extension for people to download.
@alanhamlett Could you point me to a working branch/commit where the Firefox add-on is usable? I see the following after the following steps. (I have no idea how npm works. Excuse me for posting the extensive set of steps.)
# 1. clone this repo
# 2. cd to the folder
# 3. get `npm` ready: otherwise, I get `clap not found` error
npm install
# 4. build the extension locally
npm start
# 5. Look for a zip file in: `/WakatimeBuild/chrome-wakatime/dist/firefox`
# 6. Open Firefox and visit: `about:debugging#/runtime/this-firefox`
# ==> this got me to "install" the unsigned add-on
(Note, these steps worked on a Linux Mint machine, but not on a WSL Pengwin instance. I installed npm through conda on both machines.)
Well, after these steps, I got slammed into a wall :) ==> no way to login, nor apply any white/black list.
@llinfeng do yourself a favor and find another platform other than Wakatime. There is clearly zero importance to this issue for the owner/maintainer. This has been ignored for far too long. They merged the PR to support Firefox yet, they haven't built the extension and released it.
@NeckBeardPrince I suppose WakaTime is mostly a one-man operation? I am personally amazed by the full set of editor support it provides. For now, I suppose we need some final touch from @alanhamlett?
RE: support for Firefox - I think we are close to at least getting something to work: for now, the chrome and firefox extensions look rather identical. Hopefully, they shall function in a similar manner? I was surprised to find two folders populated under chrome-wakatime/dist/ directory. Except for the "Options go here" placeholder, I would imagine one can get a working Firefox extension after building and singing the add-on himself/herself?
This reminds me of the dark time when the vimperator project was discontinued, where I was using a self-compiled and self-signed add-on on an old Firefox ESR version until that ESR version is discontinued in 2018/2019? I can live with Wakatime should it get rid of the "Options go here" sign and function properly: Firefox support is rather helpful, in particular as I find a performance improvement on Firefox when accessing a local server for Jupyterlab notebooks.
@NeckBeardPrince I suppose WakaTime is mostly a one-man operation? I am personally amazed by the full set of editor support it provides. For now, I suppose we need some final touch from @alanhamlett?
RE: support for Firefox - I think we are close to at least getting something to work: for now, the
chromeandfirefoxextensions look rather identical. Hopefully, they shall function in a similar manner? I was surprised to find two folders populated underchrome-wakatime/dist/directory. Except for the "Options go here" placeholder, I would imagine one can get a working Firefox extension after building and singing the add-on himself/herself?This reminds me of the dark time when the vimperator project was discontinued, where I was using a self-compiled and self-signed add-on on an old Firefox ESR version until that ESR version is discontinued in 2018/2019? I can live with Wakatime should it get rid of the "Options go here" sign and function properly: Firefox support is rather helpful, in particular as I find a performance improvement on Firefox when accessing a local server for Jupyterlab notebooks.
According to this there are 4.
For anyone who wonders in via google like me wondering what the heck is going on here; this worked for me.
-
git clonethe repo -
npm install -
npm run start - in firefox
about:debugging#/runtime/this-firefox - Select
Load Temporary Addonand select themainfest.jsonfile in the repo ROOT directory
The files created under dist/ using the "new" build do not work.
The files created under
dist/under the "new" build does not work and is not ready.
:( Any ideas on what's missing at this point for the build?
The files created under
dist/under the "new" build does not work and is not ready.:( Any ideas on what's missing at this point for the build?
No sorry, it looked liked the react instance was failing to mount which is why you get OPTIONS GO HERE and not your component. I didn't go any deeper than that.
FF support is ready 😎 Closing this
- Version 3.0.4 already ships with support for FF
- It is already released in FF add on official website https://addons.mozilla.org/en-US/firefox/addon/wakatimes/
https://wakatime.com/firefox should be updated due to https://addons.mozilla.org/en-US/firefox/addon/wakatimes/
Firefox display unknown host name. Is it a bug? Can chrome display host name correctly?
Firefox display unknown host name. Is it a bug? Can chrome display host name correctly?
I think you meant to open a new issue instead of adding a comment to an old closed issue.