Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firefox 56 add-on compatibility changes break CopperCu add-on #29

mike-scott opened this issue Oct 15, 2017 · 4 comments

Firefox 56 add-on compatibility changes break CopperCu add-on #29

mike-scott opened this issue Oct 15, 2017 · 4 comments


Copy link

@mike-scott mike-scott commented Oct 15, 2017

When upgrading to Firefox 56, the CopperCu add-on stops working. See Firefox 56 add-on compatibility changes:

Copy link

@mkovatsc mkovatsc commented Oct 18, 2017

WebExtension do not allow for custom protocol handlers. In some sense, Mozilla killed Copper.
There could be an ugly way where another program is encapsulated to do the UDP/CoAP messaging and have a cryptic URI in the address bar (a bit like the Copper4Chrome Extension). At the moment, I am not motivated to go down this path, though.

Also see

Copy link

@rogierc rogierc commented Jul 10, 2018

One escape for Copper users would be getting Firefox 52 ESR.
This Extended Support Release will still get security updates for quite a while.

I am using this firefox ESR version for now, because Copper is too valuable when developing CoAP applications. Hope there is going to be a durable solution in time.

Copy link

@mcr mcr commented Oct 1, 2018

The mozilla ESR page now offers Firefox 60, alas. Maybe the older one is available somewhere I couldn't see.

% sudo apt-get install firefox-esr
on a machine with access to Debian Stale (oldstable) gets me firefox 52. Don't use it as your main browser... and it co-exists with a /usr/local installed firefox from

Not the best solution, but it still works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants