November 12, 2019 at 4:44am
a few lessons learned: 1.
console.log()works fine in chrome, but not chromium (that was the first hour of my debugging). 2.
yarn watcheither lies, or builds some sort of special build in which
console logdoesn't work.
November 12, 2019 at 7:10pm
Thanks for the PRs! They're merged and I've submitted a new version of the extension to Google. It should be live in an hour or two
I made a start on this where it packages up the Firefox extension and it's source code (they make you send the source code too), but I remember running into more roadblocks. I'll look into it again in the coming weeks
November 13, 2019 at 6:54am
I'll just do a local install
also... I don't think you changed the version number before you submitted to google?
November 13, 2019 at 3:09pm
ill get back to you in a bit about FF
November 15, 2019 at 8:10pm
also, what any thoughts on how I build for FF locally?
For FF, run the build, and you should see a FirefoxExtension.zip. In Firefox, you can go to: about:addons and install that zip from the gear icon. It'll complain about the zip not being signed, which is where I stopped the last time. There's info at https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox on how to resolve this. It's a pain in the neck, but if you really care about getting it on FF, please go for it!
November 18, 2019 at 11:37pm
So it wasn't working, but then I noticed I had two versions of 1.8 installed. I removed both of them, restarted, added it back, then exited the browser, modified my
Preferencesfile to add the GHE URL to all 3 places, then started the browser and it worked. Is there any way we can make the
match siteseditable without having to muck with the Preferences file?