-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Stuck on processing #143
Comments
There is a polyfil implementation of the PoW, which should automatically be loaded on browsers without WASM support. Not sure why it isn't working. |
Let me know if there is any additional info you need to resolve this :) |
I'm facing the same (or at least a similar) problem here. I'm running the Palemoon browser (version 33.1.0), and the mCaptcha widget gets stuck on "Processing". By the way, this browser does have the WASM support, although I'm not sure if it's good/complete enough. (At least, Palemoon passes the check at mCaptcha/templates/widget/prove.ts Line 80 in 9922c23
Moreover, if I disable WASM in Firefox (version 115.4.0esr), the mCaptcha widget doesn't even initialize properly: the checkbox remains disabled, and the Developer Tools' console shows "ReferenceError: WebAssembly is not defined" in https://demo.mcaptcha.org/assets/bundle/bench.7CD63E1432397E10B1CB09A0980AAE3734398635112AA83DA77BCE4847EA3223.js . So apparently WASM detection doesn't work properly, either. |
When trying out the demo site on my Pixel6 using GrapheneOS and Vanadium (based on Chrome) as browser, it gets stuck at processing.
This is the sitekey i used:
https://demo.mcaptcha.org/widget/?sitekey=pHy0AktWyOKuxZDzFfoaewncWecCHo23
I will later try to connect from my PC to my phone to be able to open up the dev tools and provide more information.
The text was updated successfully, but these errors were encountered: