[hu3]

Sorry but this seems conflicting with what callahad replied above https://news.ycombinator.com/item?id=20394503 when answering "Will Preview be guaranteed to support extensions before Firefox for Android goes EOL?":

> I can't make any specific commitment, but there's a lot of time between now and Firefox for Android going EOL (and we haven't committed to specific timing for that, either.)

> However, we do have concrete plans for supporting adblocking as a built-in feature in the near future (https://github.com/mozilla-mobile/fenix/issues/96), which should make Preview more palatable to folks who rely on add-ons for that, even if only as a stopgap.

> More fundamentally, when considering major features like add-on support, we want to take the time to ensure that we're getting our design right at all relevant levels: Firefox Preview, the underlying GeckoView library, and the Gecko engine itself. And though development on Preview moves quickly, there's still a lot of design and development work yet to be done.

My understanding is that there's a good chance that Firefox 68, which supports extensions, will reach EOL before 69+ gets support for extensions.

[jraph]

I am reading this differently: it seems likely that Fenix supports extension before Firefox 68 goes EOL, but they don't want to make any announcement yet (maybe, because they don't really know what is going to happen).

I agree with you however. We don't have any guarantee at this point.

Please, Mozilla: don't EOL Fennec before supporting extensions on Fenix. This would be a huge mistake. Extensions are useful beyond adblocking. Chrome not supporting extensions on mobile is not a good reason to consider that Fenix would be good enough without support of extensions. Chrome is not good enough. If Fenix is not ready early enough, please consider releasing a version 69 of Fennec and then later versions until Fenix supports extensions.