Prompt to access your "Contacts" i.e "Enable Autofill using Contacts..." doesn't appear after double clicking on first name field.
Reported by
vku...@etouch.net,
Dec 29 2017
|
||||||
Issue descriptionChrome Version: 65.0.3307.0 (Official Build)Revision ccd206bc7c03001600e6dad7a37e6dc31cb11711-refs/heads/master@{#526321} (64-bit) OS:Mac(10.12.6,10.13.3) Precondition: 1. Access the Contacts application on OSX and fill in the "me" card with some valid addresses. 2.For creating a me card, create a contact with your details and then go to the menu item "Card" and make your contact as the my card by selecting "Make This my card". 3.Run the command `tccutil reset AddressBook` to reset AddressBook permissions for all applications. 4.Clear the default Chrome profile: If you are using Chrome use `rm -rf ~/Library/Application\ Support/Google/Chrome/Default/'. What steps will reproduce the problem? (1)Launch chrome after performing the steps mentioned in precondition. (2)Navigate to https://www.mycontactform.com/samples/change_address.php , double click on 'first name filed' and observe. Actual: Prompt to access your "Contacts" i.e "Enable Autofill using Contacts..." doesn't appear after double clicking on first name field. Expected: Prompt to access your "Contacts" i.e "Enable Autofill using Contacts..." should appear after double clicking on first name field. This is a Non-regression issue seen from 'M45' series i.e 45.0.2405.0 Note: Issue not seen on Win & Linux OS.
,
Jan 3 2018
+groby - please help triage.
,
Jan 3 2018
Best contact for autofill issues is probably mathp@, but... a) If this is not a regression, shouldn't this be marked as a feature request? Is there a design doc asking for the "Enable Autofill using Contacts"? (I can't find the string in our source tree) b) I'm not sure removing profiles while Chrome is running necessarily does anything. This probably doesn't affect this bug, but in general I would suggest stopping Chrome before the deletion and restarting after.
,
Jan 3 2018
Also, should probably add mathp@, that helps :) Also also: Adding erikchen@, who at some point in the distant past worked on code related to that. Also also also: It seems non-regression doesn't mean what I think it means, so reclassifying as bug.
,
Jan 3 2018
Looking in code search, I'm pretty sure we unlaunched this feature a few years ago. https://bugs.chromium.org/p/chromium/issues/detail?id=488146 Marking this as WontFix.
,
Jan 9 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by rbasuvula@chromium.org
, Dec 29 2017