Thomas Buckley-Houston b387f66c69 Launch and install webextension from client ... This means that Browsh can now be entirely run just by running the CLI binary. The client launches Firefox as a subprocess, then connects to it via the Marionette protocol, installs the webextension and finally triggers a new tab with, currently, the Google homepage in it. I was trying to set this up for automated testing as well by installing the built webextension as a temporary addon, because otherwise you need to sign the extension everytime with a unique semantic version. However for some reason I can't quite recreate the environment that MDN's `web-ext` creates. The extension installs fine but fails to load the `content.js` script, I can't find a backtrace or any other details about the failure. So for now, we're just going to have to use `web-ext` as seperate process and have the client connect to that. Which is what one should do during development anyway, so it's not a huge loss.		2018-01-21 11:56:05 +08:00
..
bundle_webextension.sh	Launch and install webextension from client	2018-01-21 11:56:05 +08:00
font_maker.py	Sample text colour using monochar block font trick	2018-01-01 22:10:10 +08:00