Hi, how to avoid textbox being considered as login field ?
I guess it is due to a bad implementation on this cocolis website, but how can I avoid the consequence on my side ? Regards
Hi, how to avoid textbox being considered as login field ?
Hi @Christop,
The team is aware of this and has opened [PM-5806] Remove the Inline Auto-fill Menu From `textarea` Fields by cagonzalezcs ¡ Pull Request #7655 ¡ bitwarden/clients ¡ GitHub.
Currently in testing by QA.
Kind regards,
Daniel
In the meantime, I think an easy fix would be to edit the stored URI to be https://www.cocolis.fr/sign-in
, and click the icon next to the URI to set its match detection to âExactâ.
Adding it as Exact avoids to have my Cocolis login to appear in the Textarea. Thatâs nice.
I had previously tested adding the URL where this Textarea issue happens (Cocolis.fr) to âNeverâ :
Go to Settings > Auto-fill and check what setting you are using for the option âDefault URI Match Detectionâ. If it is set to âBase Domainâ (which is the default), then the page that has the textarea
field will match to your URI1 (because the base domain cocolis.fr
of the webpage matches the base domain of URI1). If your login item contains multiple URIs, then the matching logic combines these individual URI matching results using a boolean OR
; therefore, even though there is no match on URI2
(because you are not using a mobile app) and no match on URI3
(because the match detection is set to âNeverâ), Bitwarden will attempt to auto-fill your account credentials on every page in the cocolis.fr
domain (as a result of the base domain match on URI1).
I have checked, I have Default URI Match detection to Base domain. I understand it is a OR between the URI. But then âNeverâ has no usage (except for when you want to get the favicon of a website by putting it in 1st position)
The âNeverâ option can also be used if you want to create bookmarks for launching relevant webpages (that should not be auto-filled), or for maintaining unused account in an âarchivedâ state (with all data still intact, but excluded from auto-filling).
Here is a feature request that you may be interested in: