Multi-window support on iPad is the main one. Less important, though it would have bugged me if they didn’t have it, is sustained Incognito tabs—which apparently they had until a couple of months ago, then removed without explanation, then added back in just 1 day ago, also without explanation. Found a thread on their forums with a whole bunch of people perplexed and asking what happened.
There are actually no alternative browser on iOS. Before the European Digital Market Act all iOS browser have to use webkit, so while you could install Firefox, Chrome and others, they were actually using Safari’s rendering engine. I believe that’s where a lot of the limitations come from.
Now with the DMA Firefox could use it’s own rendering engine but this hasn’t landed yet. I don’t know if any other browser has switched from webkit yet.
Sort of. As you say, it’s more accurate to say that they’re forced to use Safari’s rendering, but everything else is up to them, the same as how any other app would be developed. That’s how they get their own features like bookmark syncing etc.
Being able to have multiple windows of the same app is a feature Apple introduced in 2019, and obviously Safari supported it immediately. Google Chrome added support for multiple windows after a few months. I switched to Microsoft Edge once they added support for it about a year, maybe 18 months later, and have just been waiting for Firefox to finally support it so I can switch to that.
Incidentally, 2019 is also the year Firefox finally added support on their desktop browser for a CSS property (column-span) that a site I used to frequent required to work. Though by that time I no longer used that particular site.
Your first point at least is an iPad thing. Nothing is fully featured on the iPad. Not even safari. It’s thanks to that exact fact that chrome is at least mostly fully featured on the iPad. If safari had comparable function, you could bank on them blocking those features from the chrome app too. There’s a deal made somewhere.
They only know raising prices and knee-jerk reactions to competitive moves in their market space. Additional functionality for the user is only granted when it’s being used as a cudgle against their competition. Never for users benefit.
If you’re seeing new functionality on the iPad Firefox app, it’s likely because Firefox figured out a way to implement it without paying apple because they want the user to have that function. Totally different ethos.
If you’re seeing new functionality on the iPad Firefox app, it’s likely because Firefox figured out a way to implement it without paying apple because they want the user to have that function
Nothing at all remotely like that. They just don’t have enough developers to have implemented it sooner. It’s an API that Apple introduced in 2019, that Google implemented within months, Microsoft implemented within a couple of years, and Mozilla finally implemented this July.
Multi-window support on iPad is the main one. Less important, though it would have bugged me if they didn’t have it, is sustained Incognito tabs—which apparently they had until a couple of months ago, then removed without explanation, then added back in just 1 day ago, also without explanation. Found a thread on their forums with a whole bunch of people perplexed and asking what happened.
There are actually no alternative browser on iOS. Before the European Digital Market Act all iOS browser have to use webkit, so while you could install Firefox, Chrome and others, they were actually using Safari’s rendering engine. I believe that’s where a lot of the limitations come from. Now with the DMA Firefox could use it’s own rendering engine but this hasn’t landed yet. I don’t know if any other browser has switched from webkit yet.
Sort of. As you say, it’s more accurate to say that they’re forced to use Safari’s rendering, but everything else is up to them, the same as how any other app would be developed. That’s how they get their own features like bookmark syncing etc.
Being able to have multiple windows of the same app is a feature Apple introduced in 2019, and obviously Safari supported it immediately. Google Chrome added support for multiple windows after a few months. I switched to Microsoft Edge once they added support for it about a year, maybe 18 months later, and have just been waiting for Firefox to finally support it so I can switch to that.
Incidentally, 2019 is also the year Firefox finally added support on their desktop browser for a CSS property (
column-span) that a site I used to frequent required to work. Though by that time I no longer used that particular site.Your first point at least is an iPad thing. Nothing is fully featured on the iPad. Not even safari. It’s thanks to that exact fact that chrome is at least mostly fully featured on the iPad. If safari had comparable function, you could bank on them blocking those features from the chrome app too. There’s a deal made somewhere.
They only know raising prices and knee-jerk reactions to competitive moves in their market space. Additional functionality for the user is only granted when it’s being used as a cudgle against their competition. Never for users benefit.
If you’re seeing new functionality on the iPad Firefox app, it’s likely because Firefox figured out a way to implement it without paying apple because they want the user to have that function. Totally different ethos.
Nothing at all remotely like that. They just don’t have enough developers to have implemented it sooner. It’s an API that Apple introduced in 2019, that Google implemented within months, Microsoft implemented within a couple of years, and Mozilla finally implemented this July.
Regulations, like the Digital Market Act, are also a big factor.