From 3e56af2c8d591e851eda197e89b2b42ebe9aed45 Mon Sep 17 00:00:00 2001 From: Kyle Spearrin Date: Mon, 20 Nov 2017 17:27:27 -0500 Subject: [PATCH] copy update --- _articles/miscellaneous/custom-fields.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_articles/miscellaneous/custom-fields.md b/_articles/miscellaneous/custom-fields.md index 846f5d1d..aa711d31 100644 --- a/_articles/miscellaneous/custom-fields.md +++ b/_articles/miscellaneous/custom-fields.md @@ -22,7 +22,7 @@ If one of these matches is found, bitwarden will auto-fill the custom field's va ## Special name prefixes for auto-filling -When bitwarden searches for a webpage's form element to match with your custom field's name, an exact, case-insensitive comparison is done. For example, if your custom field has the name "PIN", the following form element's values (from the id, name, label, etc) will match for auto-filling: "pin", "PIN", and "Pin". However, values such as "pin2" or "mypin" will not match. +When bitwarden searches a webpage's form elements to match with your custom field's name, an exact, case-insensitive comparison is done. For example, if your custom field has the name "PIN", the following form element's values (from the id, name, label, etc) will match for auto-filling: "pin", "PIN", and "Pin". However, values such as "pin2" or "mypin" will not match. There are two special name prefixes that can give you even more control over how your custom field is auto-filled: