We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Its injected here:
keepassxc-browser/keepassxc-browser/content/keepassxc-browser.js
Lines 872 to 874 in 60355e8
As a result, all of its variables are just readable by the site, easy enough to confirm with console:
The text was updated successfully, but these errors were encountered:
See #2432
That's how passkeys work due to the need to override browser functions
Sorry, something went wrong.
There's no way to prevent this. The site must find the script and its contents.
This isn't entirely true because you can put all of the consts and functions into the (async () => { scope so that they don't leak globally.
(async () => {
@xPaw If that's true, then I'll have to inspect this further.
Successfully merging a pull request may close this issue.
Its injected here:
keepassxc-browser/keepassxc-browser/content/keepassxc-browser.js
Lines 872 to 874 in 60355e8
As a result, all of its variables are just readable by the site, easy enough to confirm with console:
The text was updated successfully, but these errors were encountered: