-
Notifications
You must be signed in to change notification settings - Fork 3
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
Autofill in browser #43
Comments
Hello, |
Oh, that's not what I meant. I am using Vanadium on GrapheneOS and whenever I use autofill from Vanadium it searches for "Vanadium" for every website. I just assumed it would be the same for every browser because Vanadium and GrapheneOS do support autofill from the browser and it works with other password managers.
15 Jul 2023, 12:09 by ***@***.***:
…
Hello,
Could you explain why it would be useful to search by i.e. "Firefox" for every browsed website? Generally I could support this behind a settings flag but I would like to understand the reason.
—
Reply to this email directly, > view it on GitHub <#43 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AM6VTXZR3GQYG7RHN4UUUTTXQJ26LANCNFSM6AAAAAA2H6FXWQ>> .
You are receiving this because you authored the thread.> Message ID: > <jenspfahl/ANOTHERpass/issues/43/1636737333> @> github> .> com>
|
I see. It should search for the domain name of the current browsed website instead (e.g. example.org when you are on https://abc.exampe.org/login). It works for the browsers I have tested but maybe the GrapheneOS-browser is different. I'll have a look into this. |
Hello,
May I make one suggestion? It would appear that autofill on websites is looking for an entry to match the name of the browser app rather than the url of the site being logged into. It would be nice to get this fixed if at all possible.
Other than that I'm enjoying using the app and I found the rationale behind it very logical and sensible.
The text was updated successfully, but these errors were encountered: