Issue metadata
Sign in to add a comment
|
[Autofill][Accessibility] Add a new address fields don't show autofill suggestion |
||||||||||||||||||||||||
Issue description- Turn on the accessibility Go to phone settings-> Accessibility -> TalkBack ->ON/OFF (for some phones like Samsung it would be settings-> Accessibility -> Vision -> TalkBack ->ON/OFF). - Launch chrome android to access amazon.com and sign in - Goto your account -> Manage address book -> add new address. - Autofill didn't work Expect autofill to work From my investigation, PageClickTracker::DidReceiveLeftMouseDownOrGestureTapInNode() isn't called.
,
Aug 25 2017
bumping priority to match internal bug 65053465
,
Aug 25 2017
,
Aug 25 2017
Nexus 6p Android OPM1.170824.002 Chrome Stable: 61.0.3163.51 I think the key part is GMS, as I understand talkback is part of GMS. if you flash to OPM1.170824.002, you should get the same GMS as mine. Let me know if you have difficult to reproduce it.
,
Sep 27 2017
,
Nov 10 2017
Could we have some update on this issue? Please note that M63 Stable approaching soon in 3 weeks. So, if we want have this change on M63 we need to fix and merge this change soon. Thanks!
,
Nov 10 2017
Re: #4, TalkBack is not part of GMS.
,
Feb 2 2018
It has been while with updates on this issue, could we have some updates, please? Thanks!
,
Feb 2 2018
,
Feb 2 2018
I still cannot reproduce this when trying on Chrome 66, Nexus 6 Android 5.1 and setting Talk Back to ON. Without talk back, the following WebAutofillClient methods get called when I tap inside <input>. UserGestureObserved UserGestureObserved DidReceiveLeftMouseDownOrGestureTapInNode FormControlElementClicked With Talkback ON I see the same method calls except that I need to double tap to instead of single tap. That being said I had done some refactoring work while adding support for OOPIFs but it is unrelated to any caller code for ChromeClientImpl::OnMouseDown. If as description suggests WebAutofillClient::DidReceiveMouseDownOrGestureTapInNode is not called then either 1- ChromeClientImpl::OnMouseDown is not called. 2- The Node passed down does not have a LocalFrame. 3- The WebLocalFrameImpl does not have a WebAutofillClient. This would seem like a hit testing issue which I am not familiar with. michaelbai@: I am currently a bit stretched and also not familiar with the code around Android+AutofillClient. Would you be able to re-triage this bug?
,
Feb 2 2018
,
Feb 2 2018
ekaramad@ I am not familiar with accessibility feature, and Autofill doesn't has specific code for autofill, could you confirm 'double tap' behavior consistent with Android platform? If so, we can close this issue.
,
Feb 13 2018
Sorry for the delayed response. I can confirm I could not reproduce the issue on Canary on neither Pixel XL running OPM 1.171019.021 Android 8.1 nor Nexus 6 running Android 5.1.1 LMY49S 3276206 dev-keys which is a developer build. I did not however try the OPM1.170824.002 which is mentioned in comment #4. michaelbai@: Are you still able to try it on OPM you mentioned in comment #4 and see whether the issue exists on Canary?
,
May 21 2018
I am closing the bug per comments #12 and #13. Please undo if the bug persists on specific OPM. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dmazz...@chromium.org
, Aug 7 2017