diff options
| author | 2023-08-16 17:41:05 -0700 | |
|---|---|---|
| committer | 2023-08-18 10:17:54 -0700 | |
| commit | b5197666967e3b47e1647d5946ac700e2b94da1b (patch) | |
| tree | 71046ac3818a014f5a436795a1b4ff9c23351b7b /libs/hwui/FrameInfoVisualizer.cpp | |
| parent | 7dce61f0a24e1c56243783feca4278542b09ec67 (diff) | |
Make disabled EditTexts fillable by Autofill
Some app developers are trying to improve the UX of the sign in flow by disabling one of the fields (e.g. password field) until the input in the other field (e.g. username) is validated (e.g. length exceeds a threshold). This makes sense.
However, such behavior presents a problem for Autofill: the fetched value currently can't be filled into a field that is disabled.
One approach can be to perform the fill of the fields sequentially, but there is no guarantee on which field the developer disables/enables. Also it's easy to come up with the examples of how this can quickly break.
Instead, this change just allows Autofill to fill the fields that are disabled. Note that Autofill already ignores the fields that are invisible. Therefore, this only affects the fields that are: a) editable, and b) visible, and c) disabled. There should be no good reason to disable a visible field for any purpose other then the input validation, in which case Autofill is expected to work.
Bug: 296097301
Bug: 286515609
Bug: 292049995
Bug: 294074377
Test: atest CtsAutoFillServiceTestCases
Change-Id: I7e1f342ab30f309b419b68cc26868feaf5a53934
Diffstat (limited to 'libs/hwui/FrameInfoVisualizer.cpp')
0 files changed, 0 insertions, 0 deletions