Does Vanadium support the Web Cryptography API

Onlyfun

I have encountered an issue where i can not access ProtonPass from Vanadium browser. Site response is the following:

<Compatibility check
Proton Pass requires a modern web browser with cutting edge support for WebCrypto (PRNG) and Web Storage.

Your browser: Chrome - 135.0.0.0

WebAssembly: Please update to a modern browser with WASM support. Learn more.
More info>

As you can see their site's not detecting Vanadium itself as well as the version detected is incorrect, correct one is 135.0.7049.38.0 which corresponds with version available on playstore and i have pointed that out for the support agent. They still responded identicaly to the site's response. Support again explicitly highlighted that in order to access ProtonPass the browser must support the Web Cryptography API in order to work with the encryption used by ProtonPass.

Has anybody dealt with this? if so, did you find a solution? Please share what you got on this one. Customer support seems useless in this case. They did not offer me to use the app instead of the browser probably because in my inquiry I clearly stated that won't accept that suggestion as a fix and refuse to install an app and demand the service to work as advertised. there is no app requirement metioned.

Now I am wondering since support states that they have successfully tested Chrome can the reason be in their incorrect Vanadium detection?

Or maybe there is an issue in Vanadium that does not allow them to detect it correctly?

Or maybe that required encryption api in not present in Vanadium?

Or is it proton's dishonest approach to steer clients into their app?

Fupira

WASM is blocked unless you allow JavaScript JIT for Proton.me. I think that's all of the actual issues.
You can tap on the little icon with two sliders, left to the URL, in Vanadium and switch the settings for JavaScript JIT easily there.

Note: It could be necessary to enable it again after a login redirect, if this isn't setting the option for the whole domain, because of Protons usage of separate subdomains per service.

This increases the attack surface, but it's the only option to use this Proton service in a webbrowser.
I'd say the impact of enabling it is negligible in this case, unless you have reasons to believe to be the target of attackers that'd be able to mitm any non-pinned https connections.