(jolla browser) Sites that aren't working

[d.geelen]

@attah

No, basically not at all. (Clarification: update of the sailfish-browser, yes - update of the browser engine from version 78, no).

(emphasis mine) Yes, that is also what I meant.

@attah

Think about it; if these sites work in Firefox 78 on anything else, that is by definition not true.

@d.geelen

However, from the perspective of a “casual user” I really don’t care for the technical reason that a site doesn’t work. If it works on pretty much everything else but not on my phone, then the problem is with the phone. I know that is may not be technically true, and you may not like it, but that is the practical truth.

That’s borderline calling it alternative facts or rejecting science.
There is definitely limit on how much garbage a browser should need to deal with (not that i think that is what is at play here).
But let’s spin that around; say you do get a browser engine update and it does diddly-squat, how does that help the casual user?

What kind of test is that? You’re intentionally crippling your competition in order to appear less bad. Do you also want to run this test on a Pentium II running Windows 98 from a 5400RPM hard disk and 16 megabytes of SDRAM? No, of course not, because that is not the realistic case that we are comparing against.

The point that I was trying to make is that if I sit down on my, or any other, relatively-recent relatively-up-to-date PC, running whatever OS and whatever browser, all of these sites will (almost certainly) work just fine. I.e. if I log on to a windows PC and open Edge and navigate to any of these sites, it will work. If I use an apple computer and open Safari, it will work. Even if I venture into my local hacker’s den and operate one of their Linux machines with Firefox it will work. I can ask for anyone of my friends phones, and it will work (this is very often good for a few laughs on my behalf when Sailfish lets me down once again). It will work on most any tablet. It will work on my TV’s built-in browser. If I had one of those fancy refrigerators with a built-in browser it would work on that.

@attah

say you do get a browser engine update and it does diddly-squat

To your point, yes, sure, I agree. I don’t care how it is fixed, so long as it is fixed, and this being Jolla’s custom browser, the onus is on them to fix it. If they don’t want to maintain it then they should just have shipped plain Firefox in the first place. (we would have gotten plugin/adblock support as a bonus).

[attah]

@d.geelen

If they don’t want to maintain it then they should just have shipped plain Firefox in the first place.

You really don’t want to understand, do you?
The reason it is “custom” is because no plain-linux mobile-usable, or even readily embeddable version of Firefox exists. There is no “plain Firefox” to ship.

I must admit i don’t follow the tirade you went on with making competition look bad and whatnot; but these two statements contradict each other:

@d.geelen

please give their 3+ year out-of-date firefox fork a much needed update

@d.geelen

I don’t care how it is fixed, so long as it is fixed

First you care, then you don’t. (And that was my point all along - either understand what you ask for, or don’t be needlessly specific)

[d.geelen]

@attah

@d.geelen

If they don’t want to maintain it then they should just have shipped plain Firefox in the first place.

You really don’t want to understand, do you?
The reason it is “custom” is because no plain-linux mobile-usable, or even readily embeddable version of Firefox exists. There is no “plain Firefox” to ship.

This will devolve into an argument with no clear right or wrong, but let’s dive in a little bit. There are already at least two mobile versions of Firefox, one for android, and one for iOS. Before that there was Fennec, which a last build was made for maemo/meego in 2016. Firefox is an open-source project, and there was no-one stopping Jolla from taking any of these versions and adapting them for Sailfish (except that that probably the former two use a wholly different UI toolkit). Fennec would probably have been the best choice since it already ran on maemo/meego.

If they had continued with Fennec, everybody (i.e. other open-mobile-OS communities) would have benefitted, and could have worked together on a usable mobile browser. Fennec would very likely be part of official Mozilla suite of browsers still if it was being actively used and developed. So then I ask you, why did they not ship with Fennec (“firefox”) but made their own fork instead?

Somehow having a half-way decent browser is still an unsolved problem for everyone except Android and iOS, and instead of working together we have all this fragmentation, the sailfish browser being just another example. Later there was the Epiphany mobile version which is based on webkit. That would also have been a good choice to adopt rather than “roll your own”.

@attah

plain-linux mobile-usable

Sailfish is also not a “plain linux”, i.e. the Sailfish browser is using the custom/proprietary silica components.

@attah

I must admit i don’t follow the tirade you went on with making competition look bad and whatnot;

You wanted to compare against Firefox 78 on other platforms, but that is not an honest comparison because everybody else is running an up-to-date version of Firefox / other browser.

@attah

but these two statements contradict each other:

@d.geelen

please give their 3+ year out-of-date firefox fork a much needed update

@d.geelen

I don’t care how it is fixed, so long as it is fixed

First you care, then you don’t. (And that was my point all along - either understand what you ask for, or don’t be needlessly specific)

They don’t contradict? I was making a suggestion (I do believe part of the problem is the age of the browser) in #1, but ultimately I don’t really care how they fix it. I don’t believe they will be able to fix many problems if they don’t update to a more recent version, after all there is 3 years of new features and bug fixes there, but perhaps they want to spend the next 3 years re-implementing that on their own? I don’t care as long as it works, but it doesn’t seem like a good investment of resources to me.

[attah]

@d.geelen

So then I ask you, why did they not ship with Fennec (“firefox”) but made their own fork instead?

It’s not really a fork. It is uplifting/retrofitting/maintaining an old embedding layer for Qt that used to exist.
Taking the Fennec bindings and bringing that forward would have exactly the same type of issues.
And most probably building along with the Android java bindings, but in some sensible language, isn’t too different either.

What basis, or even line of reasoning brings you to believe this would help?

It is not like Qt embed bindings are unhelpful to others either.

@d.geelen

You wanted to compare against Firefox 78 on other platforms, but that is not an honest comparison because everybody else is running an up-to-date version of Firefox / other browser.

Right, but not to say that what fails on desktop ESR 78 is fine that it fails here, if that is what you are thinking.
I’m saying that what works on desktop ESR 78 probably has a solution in modes 2 or 3 most likely, and might not even be helped in the slightest by an uplift.

I have now tested to update the user agent for 1001mooieteksten.nl; none of the existing compatibility ones work, but pretending to be an Iphone does. They are beyond silly to do this.

@d.geelen

I don’t believe they will be able to fix many problems if they don’t update to a more recent version

That’s what the test with desktop ESR78 will tell you. I’m pretty sure it will handle a majority of what’s reported here just dandy.

[247]

SITE :
Parcelsapp dot com

WHAT IS IT :
A site for tracking shipments

WHAT WORKS :
Everything

WHAT DOES NOT WORK :
Nothing really, but it’s so damn slow it’s a real pain to use, it’s seriously slow and sluggish

[d.geelen]

SITE:
https://www.yummly.com/

WHAT IS IT:
A site with various recipes.

WHAT WORKS:
The very first time you can load and view a page.

WHAT DOES NOT WORK:
Every subsequent page load, i.e. navigating to another recipe, shows the cloudflare protection-racket’s “Sorry, you have been blocked” page instead.

N.b. This is basically Browser is blocked by Akamai and Cloudflare

[JoOppen]

SITE:
fritz.box

WHAT IT IS:
access to FritzBox (router) via Wifi

WHAT WORKS:
site is found

WHAT DOES NOT WORK:
access results in plain white page without showing the field for entering the password and the access button

[tuplasuhveli]

SITE
Helsingin sanomat https://hs.fi
Aamulehti https://aamulehti.fi
Iltasanomat https://is.fi
Satakunnan kansa https://satakunnankansa.fi

and many smaller news sites that are not worth listing.

WHAT IS IT:
Finnish news sites owned by the biggest Finnish media company, Sanoma Oy.

WHAT DOES WORK
User is able to open the websites, if they disable javascript from the browser settings. However, the functionality of the websites is heavily restricted in this way.

WHAT DOES NOT
While having javascript enabled, only a blank page is shown.

[poetaster]

Confirmed with Fritz!os version 7.57 EDIT: also broken in Angelfish browser.

[rainemak]

These are coming from the JavsScript which gets loaded by the pages. Blanking happens right after hitting following error ( Same error but different domain ).

JavaScript error: https://www.aamulehti.fi/_next/static/chunks/main-b8e2658307c68cb0.js, line 1: TypeError: e is undefined

JavaScript error: https://www.is.fi/_next/static/chunks/main-b8e2658307c68cb0.js, line 1: TypeError: e is undefined

[David]

SITE

‘Opps!’ (will not work outside of stations)

WHAT IS IT:
Portal landing page for SNCF stations. Blocks SF from using their WiFi.

WHAT DOES WORK
The login page – it just doesn’t give you internet access.

WHAT DOES NOT

On my Win10 laptop, the page quickly redirects. On SF browser, it’s an empty page that does nothing.

[fingus]

google family link broken 2 weeks ago (https://familylink.google.com)

Confirmed with Fritz!os version 7.57 also the WLAN-Bridges

[ohnonot]

@tuplasuhveli

Helsingin sanomat https://hs.fi

Weird, it’s working here. XA2, SFOS 4.5.0.21. In Finland, over WLAN, and I changed some browser settings through the UI.

Main page, cookie dialog, and clicking on a random article.

[turmelus1]

Hs.fi works for me too suddenly. And seems like a good article, I’m glad that people are starting to wake up to what Musk really is.

[rainemak]

Just checked that hs.fi, aamulehti.fi & is.fi loads now and error that we saw earlier are gone:

JavaScript error: https://www.aamulehti.fi/_next/static/chunks/main-b8e2658307c68cb0.js, line 1: TypeError: e is undefined

JavaScript error: https://www.is.fi/_next/static/chunks/main-b8e2658307c68cb0.js, line 1: TypeError: e is undefined

[247]

SITE
Mega dot nz

WHAT IS IT
It’s a very famous cloud storage solution

WHAT DOES WORK
It loads

WHAT DOES NOT
But it loads in desktop mode without the ability to navigate the interface, so in reality it does not work at all, cause most functions are off the screen and you can’t reach them

[eson]

Works for me… kind of! I’m forwarded to mega dot io but then I get the mobile mode. The thing that is not working is the menu in upper right corner, so I can’t login or do anything else but scrolling. That might not be Jolla browser’s fault.

[247]

Had a try right now

So, went to mega dot io, then selected desktop mode on browser and logged in, it worked, but only in desktop mode, the mobile mode is still the same but cramped and completely off-screen

Still, althought workable, the desktop mode is very inconvenient

[eson]

Yes, it doesn’t work well. If you intend to actually use mega, it is afaics fully operational with Angelfish.

[PeegeeTips]

SITE

Liliputing

WHAT IS IT
Mini/mobile computing news site

WHAT DOES WORK
Page loads

WHAT DOES NOT
clicking on an article link to load a new page from the main page. browser unresponsive to link clicks.