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

Continuous Updating of PRF Compatibility Readme for Various Operating Systems and Browsers #81

Open
gkatrakazas opened this issue Oct 3, 2023 · 3 comments
Labels
documentation Improvements or additions to documentation

Comments

@gkatrakazas
Copy link
Contributor

I propose that we establish a process for continuously updating the PRF Compatibility section of our README to reflect the compatibility status with various Operating Systems and web browsers. This will help us and users stay informed about the functionality of our project across different OS and browser environments.

@gkatrakazas gkatrakazas added the documentation Improvements or additions to documentation label Oct 3, 2023
@alenhorvat
Copy link

Hi. Great product. Is it possible to detect and show the user whether the browser and authenticator are supported?

@gkatrakazas
Copy link
Contributor Author

Thank you very much for your inquiry.

Here you can find all information https://github.com/wwWallet/wallet-frontend#prf-compatibility
First, if you are asking additional information or a new table is included in the README, the answer is we have split the information into two tables: one for OS-browsers and another for OS-authenticators.

If you have seen something that doesn't work or if you've noticed something else, please let us know. We always appreciate feedback and insights that can help us improve our service and documentation.

@emlun
Copy link
Member

emlun commented Nov 24, 2023

And yes, there is also a compatibility warning shown if the browser appears to be incompatible.

It is also possible to check if the authenticator is compatible, but the frontend currently doesn't do that. Also, this check can only be done by inspecting the result of creating the passkey (to see if getClientExtensionResults().prf.enabled is present), it cannot be done before creating the passkey.

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

No branches or pull requests

3 participants