-
Notifications
You must be signed in to change notification settings - Fork 162
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
Some methods from dom.crypto are broken #668
Comments
Thanks for reporting and opening the showcase PR, much appreciated. I'm just playing with this a bit in #669 to try and understand what's wrong. Besides |
Hmm, I have isolated the code for key generation -> encryption -> decryption, and, they are working, I'll keep testing the other methods I depend on and get back to you. See:
|
Thanks, I appreciate your help 👍 |
I have tested more methods that are working:
We should be able to gather most of these into a test file. |
Sounds good. Maybe a separate |
I'm happy to prepare a PR, my only concern is, how should we run the tests given that junit doesn't support future-based tests? |
Ah, you should check the examples in |
scala-js-dom 2.0.0 deprecated the
dom.crypto.crypto
API, suggesting to use dom.crypto package instead. Unfortunately, many methods (if not all) are broken.On the other hand,
dom.crypto.crypto
anddom.webcrypto
seem to work.I'm yet to try all of the methods from these packages, I have tried some methods and all of them behave this way, it would be ideal to add test coverage for the package.
To showcase the problem, I have created a draft PR (#667), I'm happy to submit the test coverage and fix the integration but I'm not sure what's the acceptable way, I could just go linking the new packages to
GlobalCrypto
as a simple fix.Thanks.
The text was updated successfully, but these errors were encountered: