Browsers can now run their own rendering engines, which are sandboxed at the app level.
System-level HTML, like web apps on the home screen, are still using WebKit.
Which is how it should have been from the start.
PixelAlchemist@lemmy.world 3 months ago
Aren’t they all still WebKit under the hood though? Until they allow other web engines this is still just the illusion of choice.
aeronmelon@lemmy.world 3 months ago
IamAnonymous@lemmy.world 3 months ago
So are we allowed to use all extensions on Firefox? Is it same as Firefox on Andriod?
aeronmelon@lemmy.world 3 months ago
Mozilla would have to update the iOS app to both run their engine and accept their plugins.
But it will never be like the Android app because the iOS app will still be sandboxed and not allowed to run code outside of itself.
sunbeam60@lemmy.one 3 months ago
Yes they can but for now they are all still using WebKit.
abhibeckert@lemmy.world 3 months ago
Apple does allow other engines (in Europe). Wether or not FireFox chooses to create one remains to be seen.
I kinda hope they don’t - because the FireFox engine sucks.
Scrollone@feddit.it 3 months ago
There’s nothing wrong with WebKit
Weeeeeeelllll… actually yes, because Chrome is based on an ancient WebKit version, and Firefox is the only independent remaining browser.
uis@lemm.ee 3 months ago
Aren’t they all KHTML under the hood? Yes, they are. Except firefox.
KingThrillgore@lemmy.ml 3 months ago
Firefox uses Gecko and someday, it will use Servo. Brave uses Blink, which is Google’s WebKit fork.
PixelAlchemist@lemmy.world 3 months ago
*on desktop
darkevilmac@lemmy.zip 3 months ago
I believe part of the DMA means that they’re allowed to use their own engines. Whether they have that ready right now I’m not sure, but I’m sure it’s in the works.