|
|
|
|
|
|
by lawl
2144 days ago
|
|
|
> 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). |
|
|
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.