Adam Argyle

branch with a netlify plugin added https://github.com/GoogleChromeLabs/ProjectVisBug/tree/netlify-plugin

what's the flow for getting a token? what if i made a visbug account and let everyone piggy back off it (all plugin pushes use my token)? lol, when would...

sounds like a cloud function + a secret could make this all much less painful?.. how often does one need to fetch the referrer?

VisBug works on the DOM 😉 we could totally setup a cloud function that owns a secret, question is, do i want to own and maintain it. even though it's...

if visbug chooses the serialize/deserialize route, there's a few ways to attack it. and yep, in another branch i'm hacking on a pub/sub visbug api (which includes a serialization of...

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

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...

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,...

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

we have a new lead to get around the issue, we're going to try injecting visbug from the content script, like ```js var script = document.createElement('script'); script.src = chrome.runtime.getURL('bundle.js); document.body.appendChild(script);...