-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Autocomplete fails for umlaut domains #910
Comments
Can you provide an example website where I can test this, please? |
When I visit this website, in my browser tools if I check
Any idea why? |
I guess that is the puny code version of the domain. The browser doesn't report it the way that includes the umlaut. |
Yes https://obs.xn--brgerhaus-q9a.de/ is the puny code version of the domain. If I store this one as url in the vault record, the autocomplete is successful. |
For now, we can only support puny code versions of the domain. An external library would be required to decode it back if we wanted to support it further in the future. |
Are there no external libs yet? |
As a workaround, is there somewhere we can convert a domain with accents to its puny code version ? Non ascii characters in domain names will likely appear more and more |
If you view the website in your browser then open Bitwarden, click "Add New" from the "current tab" page. The prefilled info for the website is the puny code version, which is what the browser reports the domain as. |
Hello! Autocomplete not working when I'm using russian punycode in Regular Expressions. |
Hi @magicsunday, |
If I store a password for a umlaut domain (a domain containing ä, ö or ü), the password autocomplete fails. If have to use the puny code style type of the domain to get it working. Which is not very handy.
Seems not only a issue in the browser extension, but also in the IOS app.
The text was updated successfully, but these errors were encountered: