Does app.element.io still work in Firefox?
At first I thought they were blocking the IP-address range of VPN nodes that I'm using, but now that I've tried switching to a different one, I think something else is at play here.
It doesn't give me any meaningful error — it just looks like a blank page, the only error I see in the console is:
Uncaught TypeError: Intl.Segmenter is not a constructor
node_modules bundle.js:2
Webpack 21
Could this be it? 🤔
OMG, it's not just me and it's… disgusting:
https://github.com/element-hq/element-web/issues/27684
Apparently, their policy is to only support two latest releases of Firefox and Chrome, so the fact that it had worked for me is just a coincidence!
The "that browsed is a year old already" line is simply priceless!
The most fun part is that this update coincided with the new FF ESR, so their solution is: just install the new ad-ridden FF — or Chrome even, what is your problem?😤
Oh my, this is such a trainwreck!
#element #matrix
@m0xee switch to a suitable fork, not updating a browser is a bad idea anyways
@kitkat
…I was safe because I had support for WebP disabled😁
AND they have made it non-optional right after this was discovered. One of the major reasons why I started building Firefox myself was to bring the preference to disable WebP back.
That's the problem — no one has problem with updates when they are security updates, but they often come with feature updates: support for new things that no one asked for or changes in the UI — at times rather serious ones, which might ruin your workflows.