Because the new Firefox WebExtension format is mostly compatible with Chrome’s extension format, this seems to be working with no changes.
-
-
Replying to @dietrich @swborders
Would you mind submitting a pull request with the small adjustments or changes you made? We can review and publish updated materials.
1 reply 0 retweets 0 likes -
Replying to @blockadeio @swborders
I would... but I didn't make any changes
Yay for standardizing APIs! I only tested that it started up without errors. Is there a test suite I can run? Happy to do further testing if you point me in the right direction.1 reply 0 retweets 0 likes -
Replying to @dietrich @swborders
No suite unfortunately. We'll repeat on our end with the latest Firefox and identify any adjustments needed.
1 reply 0 retweets 0 likes -
-
Replying to @dietrich @swborders
Testing with the
@firefox extension tester shows no issues, but installing reveals some behaviors that seem to indicate errors. Going to kick this around a bit to see what the issues are.1 reply 0 retweets 0 likes -
Ok, kick it over here if you need me to dig intoit. Feel free to dm or email dietrich@mozilla.com.
1 reply 0 retweets 1 like -
Got a submission in. Managed to get everything working apart from displaying the actual local warning page when a user visits a bad page. For some reason FF doesn't respect redirects to local pages. Github updated, live: https://addons.mozilla.org/en-US/firefox/addon/blockade-io/ …
1 reply 0 retweets 0 likes -
Yay, so close! I’ll file a bug for the redirect, and try and come up with a reduced test case. Going from http(s) to an internal extension URL, yah?
1 reply 0 retweets 1 like -
Replying to @dietrich @blockadeio and1 reply 0 retweets 1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.