That’s not the reason; Safari and the like still support the WebExtensions API. They just require extensions to be signed, .app’d, etc and only go to Safari which is a lot.
Comment on Open extensions on Firefox for Android will be available from December 14
TrickDacy@lemmy.world 1 year agoNot until apple allows non-webkit browsers like an operating system would. It’s happening but I’m not sure when.
PS it can only happen because the EU forced them. that’s right, your os maker had to be forced by the government to allow basic computing functionality. Apple is shitty.
Aatube@kbin.social 1 year ago
TrickDacy@lemmy.world 1 year ago
I read this over and over and it makes no sense to me. Even if you were right, do we really think that FF extension devs are going to make and maintain a completely separate codebase for a iOS-only FF version of each extension? I highly, highly, doubt anyone would do that.
Then on top of it, yeah, maybe you’d have to kiss Apple’s ass to ever get it installed on a user’s device. In any case, Fuck apple with a cactus.
Aatube@kbin.social 1 year ago
It’s the same codebase. Safari can use extensions written for Firefox as long as you compile it into Apple format.
TrickDacy@lemmy.world 1 year ago
Bizarre. All these years, every time I have tried to use a safari extension, even very popular ones like 1password, I’ve had issues. So I feel like it’s historically not been as simple as this… Maybe it is now, but all the web devs I know HATE safari. Myself included.
Sabata11792@kbin.social 1 year ago
ItS InNoVaTiVe and ViSiOnAry.
netchami@sh.itjust.works 1 year ago
They are innovative, they always find new methods to get more and more money from their customers