Describe the bug
Matrix.to is broken on Firefox 60esr and all versions before 74 and Chromium 73 and all versions before 80, the page doesn't have any text.
function s(...e) {
const t = {};
for (const i of e) {
if ("string" != typeof i) throw new Error("Invalid enum value name" + i?.toString());
// ^___ error raised here
t[i] = i
}
return Object.freeze(t)
}
In my opinion, having a bundle and using these new functions negates the point of simplicity mentioned in the README. The matrix.to links were not broken before the redesign, and while a quite happy Matrix user for a few years now, having the links broken client-side gives a bad image to new potential users about the Matrix ecosystem.
Unfortunately, there's a trend since last year about websites carelessly breaking client-side while this being completely avoidable (usually missing polyfills or worse using new syntax like here), privileging developers happiness to users usability, and it saddens me quite a bit to see Matrix in the same wagon while I am a big fan and proponent of it.
Describe the bug Matrix.to is broken on Firefox 60esr and all versions before 74 and Chromium 73 and all versions before 80, the page doesn't have any text.
To Reproduce Steps to reproduce the behavior:
Expected behavior Page is properly displayed without issue
Desktop:
Desktop:
Additional context Matrix.to uses optional chaining (?.), only supported by 85.03% of browsers/users globally according to caniuse. Support in Firefox was introduced with Firefox 74.0 only released 2020-03-10. Support in Chrome/ium was introduced with Chromium 80 only released 2020-02-04.
The issue comes from the following beautified function in https://matrix.to/bundle-esm-3551970109.js
In my opinion, having a bundle and using these new functions negates the point of simplicity mentioned in the README. The matrix.to links were not broken before the redesign, and while a quite happy Matrix user for a few years now, having the links broken client-side gives a bad image to new potential users about the Matrix ecosystem.
There are basically two solutions for this:
While it may be argued that a new version of Firefox ESR is available in Debian 9 repositories (though Mozilla is unfortunately removing a lot of things I use every few versions, so I am really reluctant about upgrading because of this), this is not the case for Chromium.
Unfortunately, there's a trend since last year about websites carelessly breaking client-side while this being completely avoidable (usually missing polyfills or worse using new syntax like here), privileging developers happiness to users usability, and it saddens me quite a bit to see Matrix in the same wagon while I am a big fan and proponent of it.