[tialaramex]

So, because Firefox on your phone doesn't have X, you deleted it everywhere and installed a browser that... also doesn't have X?

FWIW This is one of the symmetries when we have to do policy shifts like TLS 1.0 deprecation. Even though every major browser will implement the policy and has announced that, some fraction of users will feel "betrayed" and switch from one browser implementing the policy to another browser also implementing the policy.

It's worse if you have defectors (e.g. back when Microsoft had Internet Explorer you could rely on IE being last to actually implement even if it had previously announced a timeline right in the middle of the ballpark, customers would push back and somewhere a Microsoft exec decides that hey, making a customer happy is more important than security) but it happens even for a more or less simultaneous policy change.

Guaranteed some CAs will lose customers over Apple's 398 day certificate expiry policy, even though it affects every CA equally at the same moment.

[lawl]

> So, because Firefox on your phone doesn't have X, you deleted it everywhere and installed a browser that... also doesn't have X?

No, because Firefox on my phone has removed X, I'm switchting to a browser that's getting X, and where the time-line isn't "we dunno lul". Maybe Brave doesn't hit their timeline, but Mozilla doesn't have one and I have no idea when my stuff will start working again. Until Brave Mobile has extension support I've downgraded my FF on mobile to the EOL version.

But as I said, it was the last straw that broke the camels back, I do not consider Mozilla to be trustworthy anymore, and this was just the latest in a series of issues.

I don't see how this is in any way similar to TLS 1.0 deprecation, because sites should have upgraded. There's nothing extension authors could have done. This is fully Mozilla dropping the ball (once again).

[franga2000]

Except that FF is also getting the feature - according to their timeline around Q4 20 - Q1 21.

As many have pointed out, Mozilla updated your glitchy and slow browser with a newer and faster one that unfortunately still isn't at feature parity. They didn't remove the feature in the sense that they abandoned it, it was simply a regression that came with an update they considered more important. I agree it was way too soon to push Fenix to stable users, but switching to fancy Chrome just because of one FF regression that will be fixed seems a bit much.

[Multicomp]

I agree with you, hence why I disable the auto update for my Firefox app.

The blessed extensions strategy is one I would have avoided.

[shock]

> As many have pointed out, Mozilla updated your glitchy and slow browser with a newer and faster one

I don't need Mozilla to make my decisions for me.