-
Notifications
You must be signed in to change notification settings - Fork 11
WebExtensions are the future! #29
Comments
Any news? @catholicon Firefox 57 will be released soon. |
Now it happened: update to Firefox 57 and OfflineQR stopped working :-( |
I'm so sorry guys. I've not been able to work on it at all. But, for what it's worth, I would do it as soon as possible for me to get some time at my hand. |
Note that there are already many, many new WebExtension QR Code add-ons for Firefox. I also noticed this one claiming to generate these QR codes offline, but unfortunately the developer does not really want to release the source on GitHub or so. |
We want your code working with Firefox >= 57.0. |
There is a good addon can be used as replacement: |
BTW I made a fresh new QR code add-on, which also works offline, but has a nice UI, too: https://github.com/rugk/offline-qr-code |
Thanks, rugk! Works very well, small, compact, no frills- already became my favorite QR generator! |
Just create an issue in my GitHub repo if you can reproduce any bugs. (or look, if I already created one) |
Edit: Below you can find a proper replacement for this add-on!
The current plan is that Firefox 57 will only support web extensions. Your add-on is not a web extension yet as far as I can see, so you should consider remaking your add-on. The Firefox 57 release is planned for 28th November 2017.
Already since Firefox 53 (planned release: 18th April 2017) AMO (addons.mozilla.org) no longer accept other new add-on submissions than web extensions. Old extensions can however still be updated.
The good message is that one should be able to use your web extensions add-on in all mayor browsers. That's the idea behind web extensions.
Note that you can use so-called hybrid extensions for switching to WebExtensions.
Note that all dates are estimates and may be changed.
German source: https://www.soeren-hentzschel.at/firefox/firefox-57-mit-exklusiver-webextension-unterstuetzung/
Original source: https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/
The text was updated successfully, but these errors were encountered: