There are two issued scenerios:
1. User saved username without "@gmail.com" for google.com on Samsung Pass.
Example : username is "aaa"
When autofill do username matching, potential_suggestion(from pass_agent)
will be "aaa", but current_username(from username element) will be
"aaa@gmail.com".
Username matching fails, so that autofill will fail.
2. User saved username as a phone number for website on Samsung Pass.
Example : username is "151xxxxxxxx"
When autofill do username matching, potential_suggestion(from pass_agent)
will be "151xxxxxxxx", but current_username(from username element) will be
"+86 151 xxx xxx xx".
Username matching fails, so that autofill will fail.
Since Tizen autofill will get both username and password from pass_agent,
there is no need to do username matching before fill in password
Change-Id: Iae8f1d6573bee11c541995520e97691d93125ba9
Signed-off-by: Liu Feifei <feifei08.liu@samsung.com>
LOG(INFO) << "[Autofill] potential_suggestion : " << potential_suggestion
<< ", current_username = " << current_username
<< ", exact_match = " << (int)exact_match;
+#if BUILDFLAG(IS_TIZEN_TV)
+ return true;
+#endif
if (potential_suggestion == current_username)
return true;
return !exact_match && IsPrefixOfEmailEndingWithAtSign(current_username,