one.element.io doesn't start anymore in Firefox 128

[sd2k9]

Steps to reproduce

Since around the Element Web update around 18.07.2024
I cannot use Element Web at https://one.element.io/ anymore.

Clearing browser cache or stored data doesn't help.

Can I somehow find out why Element thinks that the latest Firefox release is not a supported browser?

Thank you!

Outcome

What did you expect?

Login to Matrix Element One

What happened instead?

Looking at the firefox console I can see the following error:

Error: Unsupported browser
    c compat.ts:34
    a BackgroundAudio.ts:27
    q Notifier.ts:116
    ts Notifier.ts:535
    Webpack 3
[rageshake.ts:77:16](webpack://element-web/react-sdk/src/rageshake/rageshake.ts)
    t rageshake.ts:77
    <anonymous> logger.ts:97
    ts index.ts:231

Operating system

Debian GNU/Linux 12 (bookworm)

Browser information

Firefox 128.0 (64-bit)

URL for webapp

https://one.element.io

Application version

Element version: 1.11.71

Homeserver

Element One

Will you send logs?

No

[sd2k9]

Complete output of Firefox Console is attached. Is there anything else I can provide or check myself? Thanks!

firefox_console.txt

[t3chguy]

Duplicate of #27793
Your browser has a required feature disabled, this feature isn't optional in the web spec.

[sd2k9]

Thanks @t3chguy, that helped me!
Sorry for missing #27793 when I looked for a solution.

For anybody interested: The relevant about:config setting is dom.webaudio.enabled
You can disable it after loading the Element page.
Same for also recently required javascript.options.wasm

Still, it would be nice to find such kind of information somewhere on the failing page instead of a unspecific (and wrong) "browser not supported" message. Maybe in some debug context or browser console if you want to hide this from the average user?

Can you please consider this for future improvements?

[t3chguy]

Maintaining how to modify your browser back to stock is not feasible for such a small team. Browsers don't agree on such internal behaviours and they are not the same between browsers. Different options appear with every update.

[sd2k9]

I understand - and agree - that giving instructions about settings for all browsers out there is not feasible.

I was just wondering, wouldn't it be possible to give more details about a failure? Like a "Your browser is missing WebAudio" instead of "unsupported browser"? This should make debugging (and solving) of problems much easier for everybody - would I have gotten this message I could have solved the problem myself without the need of your help.
Isn't this especially helpful for a small team, giving your users the knowledge to solve as many issues as possible by themself?

There are restricted environments out there where returning to stock is not possible, but modifying some settings may be.

Anyway, again thanks for your help and your consideration of my suggestion.

[t3chguy]

We already have a WebAudio Modernizr check loaded which should do exactly that, its just a case of a new release coming out to make use of them.

[mpeter50]

We already have a WebAudio Modernizr check loaded which should do exactly that, its just a case of a new release coming out to make use of them.

If you mean an error message in the console, I guess thats something, but its not really visible, and it can be hard to find among the few dozen other messages when you are supposed to be doing something else than debugging software.

In that case, I think having this text message about the missing feature on the displayed webpage besides the "Unsupported browser" text would be more helpful.

[t3chguy]

@mpeter50 riot.grin.hu is on 1.11.72 which is 2 versions out of date so doesn't have the latest error I spoke about earlier.

[mpeter50]

Oh, sorry. I thought "Enable audio/webaudio Modernizr rule (#27772)" in the changelog was about that.

[mpeter50]

I think this is still happening on app.element.io, which runs Element version 1.11.76.
If webaudio is disabled, the page still only shows a generic "unsupported" message, while the console logs the lack of webaudio support:

app.element.io page error message	developer console output

Should I open an issue for this? Asking in case I have just overlooked something.