Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encryption broken on develop.element.io in browsers without WASM support #17463

Closed
jrick opened this issue May 25, 2021 · 1 comment · Fixed by #17502
Closed

Encryption broken on develop.element.io in browsers without WASM support #17463

jrick opened this issue May 25, 2021 · 1 comment · Fixed by #17502
Labels

Comments

@jrick
Copy link

jrick commented May 25, 2021

2021-05-25-093012_656x562_scrot

Description

The Chromium package on OpenBSD disables wasm support by default (for several reasons I won't go into here). It is possible to re-enable it, but I would prefer to leave it off.

The latest development version of Element Web no longer works with this setup. The fallback to loading olm_legacy.js (https://develop.element.io/olm_legacy.js) is 404ing.

Steps to reproduce

  • Use OpenBSD chromium, or any other chromium browser with --disable-features=WebAssembly,AsmJsToWebAssembly,WebAssemblyStreaming --js-flags=--noexpose-wasm.
  • Open Element Web (currently, Element version: f78be2631ad6-react-1751b4ba43ea-js-acb9bc8cc523)

Logs being sent: no

Version information

  • Platform: web
  • OS: any (but only tested OpenBSD)
  • Version: f78be2631ad6-react-1751b4ba43ea-js-acb9bc8cc523
@jrick jrick added the T-Defect label May 25, 2021
@brandsimon
Copy link

Normal app.element.io does also not work when disabling wasm support on my side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants