Browser limits phone usability

AppLee

Don't you worry you're not disqualified in any way.
I just wanted to point out and you mentioned it in your reply:
We cannot hold any apple to apple comparison with iOS and Android.
We are a community driven Open Source project, we don't have billions and not even millions we have people, good people, but very few of those.

Ubuntu Touch may or may not be for you because ATM some website you rely on don't work anymore on Morph.
That's a pity but we cannot make things go faster with a magical wand.
I understand perfectly your point of view and reporting issues is a good thing.
But the way you did it could be seen as nagging and that's not great.

In order to report things properly, it's best to open issues on Gitlab with logs and details.
This is not something we can expect from everyone (we know that), that's why I'm currently working on a app to help "regular users" to report bugs the "right way".
We are trying to bridge a gap between developers and regulars folks we're not perfect but we try to be as transparent as possible as to what one can expect from the OS. And yes it changes with time and new online services.
I think I already mentioned but sometimes even Firefox is not supported ; who is to blame? I'm inclined to say the website...

So basically I just wanted to remind everyone that we are one and we have to put ourselves in other members' shoes.

And some users are happy with the current state of Ubuntu despite VoLTE and the browser and the lack of Whats~~That~~App.
Because what works, works pretty well despite limitations that we're trying to push (and you are part of the we)

@messayisto On the Open Store, if you search an app made by Alfred there is sometimes a link to donate.
I'm not sure it should be on the forum, but ; here it is: https://paypal.me/beidl
The browser is not et on the Open Store and it might take some time...

jojumaxx

@AppLee Thank you for your answer, I really appreciate it.
No, it wasn't supposed to be nagging. I apologize for that.

Of course UT is for me, it's my daily driver for so many years now. It's stable and reliable and pretty.

Absolutely basic features should be priority no. 1. And since I am not involved in development I can't tell if there was no possibility to focus on that earlier, but then no magic wand was on the wishlist today...

I started diving into the Linux and FOSS world many years ago, but as a user only. And still I am learning about how all this works today and about philosophies behind it...
Though I have very little time, I am trying to get into app development. And hopefully I get to the point that I can give back a bit more.

I'll get along until a new browser emerges...

P.S. I only compared to de-googled OSes (I'm aware they have another basis which offers a lot). The comparison to apples is made on the website

arubislander

@jojumaxx In addition to what @AppLee has already said, I would like to add some context as to why the state of the browser is the way it is at the moment.

Morph is based on QtWebEngine, which is part of the Qt Framework that powers the UI of Ubuntu Touch. QtWebEngine uses the same web renderer as Chrome. As part of the framework it is pinned to the major Qt version that the base distro ships with. Ubuntu 20.04 and 24.04 both ship with Qt 5.x (different .x for each, but it is the 5 that matters here)
Development on Qt 5 has ceased, the current version is now 6.x. However, that will probably not be shipped till Ubuntu 26.04. It will take that long before it becomes relevant to us.

In the past the UT developers have tried to keep QtWebEngine updated ahead of the rest of the framework, to ensure a functioning browser which is reasonably up to date. (I think currently QtWebEngine is at 5.15 while the rest of the framework is at 5.12), This was feasible as long as the major versions were the same.

Lifting Lomiri to Qt 6 is a huge endeavor, and to be honest Qt 6 might not yet even be ready with all necessary components. And updating only QtWebEngine to Qt 6.x would introduce difficult to resolve conflicts due to mixing Qt versions.

So for the foreseeable future we are stuck on QtWebEngine 5.x. At the very least for the next few development rounds. The devs are aware of the situation and are regularly floating ideas to mitigate the issue. Alfred's browser that uses WebKit like Safari is one such initiative. But it has yet to reach the OpenStore as stated earlier.

In the meantime what options do you have while staying on Ubuntu Touch? I guess Waydroid is the only option that comes to mind. With that you can have Chrome or Firefox mobile or any other browser that runs on Android for those sites that no longer work in Morph.

jojumaxx

@arubislander Thank you for that explanation. I wasn't aware there was a focus like that on QtWeb...
So there is kind of a gap development is stuck in between Qt5 and Qt6?

Beginner's question:
If Ubuntu itself comes with Qt5, too, why do the browsers not have these issues?

I wanted to avoid *.droid. I tried it nevertheless some time ago, but my Volla with it's 4GB Ram struggled. That was pretty laggy. Maybe that changed on 20.04.

domubpkm

@jojumaxx

Maybe that changed on 20.04.

I would like to be very sure that you are on 20.04, because 16.04 is the worst for the browser now.

A solution: I see you have two Vollas. In this case, to not use waydroid, use one Volla under Volla OS to have updates browsers, another under UT.

arubislander

@jojumaxx said in Browser limits phone usability:

Beginner's question:
If Ubuntu itself comes with Qt5, too, why do the browsers not have these issues?

Excellent question. The answer is because most people use Chrome / Chromium and Firefox on desktop Ubuntu, none of these use QtWebEngine. Instead, both browsers bundle their own version of their separate browser engines (Blink for Chrome/Chromium and Gecko for Firefox). So when the browser updates, the browser engine updates independently from the base OS.

But browser engines are huge beasts, and especially early versions UT came on storage constrained devices, making it necessary to save space in the root filesystem where possible. (This is still a relevant consideration due to the wide range of devices UT runs on.)
Also, because of architectural reasons for supporting web apps, the choice was made for the flagship browser to use the browser engine that came packaged with the system, i.e. QtWebEngine.

messayisto

@AppLee thank you!

jojumaxx

@arubislander Thank you. I learned a lot in this thread and understand things better now.

I want to thank everybody for their patience and the hard work. This helps to appreciate it even more.

arubislander

@jojumaxx One option I haven't seen mentioned yet is making a web app / bookmark app with Webber. If a recent enough User-Agent header is added, most websites work.

jojumaxx

@arubislander I uninstalled Webber some time ago and started to use simple browser bookmarks.
The reason is, that you have to add every URL ((sub-)domain) a website might use. Otherwise there's a fallback to the browser which has no passwords (cookies) stored, keeps opening new tabs etc. which is an annoying behaviour.
E.g. for eBay I had more than 20 URLs. And always another one came up (hard to catch due to forwarding) and I had a fallback to Morph again. To add a new URL I had to create the Webber-Shortcut again and add every single URL...
If Webber was able to reopen a shortcut with all settings made, that would be a game changer (or didn't I just see that option?).

I could revive this if your suggestion works, but I'm afraid you have to tell me how to add the user agent header and which one (maybe there are options in Webber. I have to install and check first)...