This is a WebExtension (both chrome and firefox supported), which allows you to find out how much clicks you make on the web. Looks like this:
But what counts as "click on the web"?
- Mouse click or emulated "click" event
- Made on a website - browser UI or internal browser URL's don't count
- Made using a primary button (left button), or:
- The one that triggers "contextmenu" event (right click)
This extension was tested on Firefox 48 and Chromium 52.
You need to download or clone this repo first. Like this:
git clone https://github.com/zb3/ClickCounter.git
I didn't pay Google $5, so this extension is not published on webstore, but we can install it anyway:
- Go to
chrome://extensions
- Drag file named
cc.crx
into that page UninstallEnjoy!
alternatively, you could enable the "Developer mode" there and click on Load unpacked extension... button, then select this project's directory.
- Go to
about:debugging
- Click Load Temporary Add-on
- Select any file in the project's directory.
Oh, this is a little harder, because I didn't submit this to AMO, and I didn't sign this either. But since we're advanced users, we can do everything, including installing ClickCounter
on Firefox.
-
Make sure you have a version of Firefox that doesn't require signing addons:
- On Windows this is trivial - just use Beta or Developer version
- On Linux the above is not always easy, fortunately there's a crack. After running that you'll also need to set
xpinstall.signatures.required
tofalse
inabout:config
. And of course, after browser update, you'll need to reapply the crack. But this is fun!
Or just sign the
cc.xpi
file by submitting it to Mozilla. :) -
Drag the file named
cc.xpi
into the browser
Some domain names are long so they don't fit, and you should then see ...
in that domain name. But if you copy that, whole domain name will be copied. Thanks to text-overflow
magic!
To pack the extension, use:
./pack_ff.sh
./pack_chrome.sh #requires "chromium" installed
Note that manifest.ff.json
is not a JSON file (makes sense, right?), it contains FF specific addition, namely addon ID, which is required for unsigned addons.
But we need this only for xpi
packed addons, you can still use about:debugging
+ Load Temporary Add-on with chrome-compatible manifest.json
file.
For chrome, Load unpacked extension should work just fine.