# New break of compatibility for add-on / webextensions

**URL:** <https://discourse.mozilla.org/t/new-break-of-compatibility-for-add-on-webextensions/72545>\
**Category:** Firefox On Android\
**Tags:** webextensions-api, issue\
**Created:** [December 21, 2020, 3:40pm UTC](https://discourse.mozilla.org/t/new-break-of-compatibility-for-add-on-webextensions/72545 "2020-12-21T15:40:15Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![anon18296772](https://avatars.discourse-cdn.com/v4/letter/a/8c91f0/32.png) [@anon18296772](https://discourse.mozilla.org/u/anon18296772)\
**Post date:** [December 23, 2020, 12:01am UTC](https://discourse.mozilla.org/t/new-break-of-compatibility-for-add-on-webextensions/72545/4 "2020-12-23T00:01:25Z")

</div>

> [@plwt](#):
>
> how to do this in a way that avoids the security and compatibility issues

If this is a good enough reason to make many users unhappy in 2020, then it sure sounds good enough a justification for 2021 too, and the following years.

Before long there will be a feature-frozen _“waterfox for android”_ so people can just run one piece of browser software and never ever “update” it at all henceforth!

Or simply this fork: [GitHub - fork-maintainers/iceraven-browser: Iceraven Browser](https://github.com/fork-maintainers/iceraven-browser#readme)

Must be like heaven! 🏝 🏖 🎡

The main thread for this subject starts with [an innocuously worded headline…](https://discourse.mozilla.org/t/add-on-support-in-new-firefox-for-android/53488/133)

---

_[View the full topic](https://discourse.mozilla.org/t/new-break-of-compatibility-for-add-on-webextensions/72545)._