Firefox extension

[argyleink]

Verified the custom element renders and is fully operational, so it needs an extension build process created, needs a firefox extension lifecycle integration, and some marketing assets to prep for publishing.

[lannonbr]

Would to love use this across both Chrome and Firefox

[argyleink]

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Porting_a_Google_Chrome_extension
LOE is low, gotta do this soon!

[argyleink]

workin on this, there's bugs:

• browser defaults are different between chrome and firefox, so this prop map needs updated... https://github.com/GoogleChromeLabs/ProjectVisBug/blob/master/app/utilities/design-properties.js#L5
• firefox addon doesnt seem to like adding a custom element... very hard to debug error happening where the ToolPalette class initializes but doesnt seem to think it has class methods..
• up and down on the keyboard (with fonts at least) can cause the page to move

https://github.com/argyleink/ProjectVisBug/tree/feature/firefox-extension

[argyleink]

steps to setup dev env:

• setup https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Getting_started_with_web-ext#Testing_out_an_extension
• then run web-ext run
  • will open Firefox with extension installed
  • double check by visiting about:debugging in the url bar, then click "debug"
  • as well as about:addons
• visit a webpage
• click the puzzle piece in the top right (should say VisBug when hovered)
• then go look at your logs: one in the debug window from firefox, other is the console of the page

hope that helps someone...

[hfiguiere]

For the icon, I have that commit to fix it:
hfiguiere@0e25e52

[argyleink]

turns out custom element classes are having a hard time initializing in content script environments
link to issue known by firefox team https://bugzilla.mozilla.org/show_bug.cgi?id=1492002#c7

[kud]

Thank you for your work @argyleink I can't wait to see it on firefox!