I don’t see other topic like this (or at least not totally outdated), so here it goes.
Is it possible to run main branch of Firefox compiled for ARM (whatever device uses) on SFOS currently? Probably few people are aware of how hard would it be to run this (mobile-config-firefox) Making sure you're not a bot! (don’t mind the name of the link, it leads to gitlab)
I’m super annoyed by the browser, I know it will be updated in some time. It’s so bad right now, that web version of LocalSend doesn’t display correctly in Jolla Browser… Anyway, don’t beat the dead horse.
It would be nice to have a Firefox browser with extensions like a first class citizen, not a Firefox based Safari - yes, I’m mocking Jolla browser here, because it kinda is a Safari here or worse - the default OS browser, which it actually is. Now. There is generally nothing wrong with the concept of default browser, but the problem is - we always need to wait for an update from Jolla, and (as we can see I guess) devs also have other stuff to do.
So here it is - is it possible to make it running currently, or IDK - SFOS dependencies are so outdated, that it wouldn’t run or something? Because as far as I see it - Gnome Mobile, Plasma Mobile are going to more or less develop further, and some people are going to probably develop this mobile config for Firefox further. It would be nice to have a browser that doesn’t need AAS, and doesn’t need to wait for Jolla to develop it.
Come talk to me, share your thoughts.
Also I’m not a developer of anything, and if I could do something, then It would be probably compiling some stuff from source with a good documentation on how to do it. Nothing more (for now).
I know about it and people here say it’s even worse in terms of being up to date then Jolla Browser - probably until Jolla will update Qt dependencies, because on their Gitlab it looks like Angelfish is being developed.
To address your specific issue with LocalSend Web, I have accustomed to use a combination of scp and https://pairdrop.net on my devices, and the latter works wonderfully in Sailfish Browser.
At my university I can also tell people with Macbooks, just visit that webpage to send me stuff, they don’t have to install anything.
Browsers are famously complicated to build. IIRC Firefox was the only thing to have an exception from building on the same Debian version it was building for some time way back when - possibly still.
Of course adapting the embed bindings to new versions is the biggest task; but getting all the dependencies up to date is no small task either - and that you wouldn’t get away from.
Personally i don’t miss plugins very much. I can’t speak to the UI, but it seems to me it would fall apart rather quickly after the main functions wen run (even if adapted) to such a small screen.
Honestly i’m torn. The current situation is no good - and the alternative has drawbacks too.
Oh, so I have been fooled by some posts here. Sorry.
I thought that it requires those as dependencies.
How does it come with it’s own libraries? Because if via Flatpak, then it’s understandable.
I’m missing something.