Create a separate structure that tracks the current generation status for a
field in PasswordGenerationAgent. Currently |generation_element_| has a double meaning. It's an element that should trigger the automatic generation. However, if a manual generation is triggered then it's overwritten by a password field. That's confusing. The CL decouples the field that should trigger the automatic generation from whatever is happening right now on a random password field. In the future that will allow us to have multiple generation elements simultaneously. For now it fixes 870220 where the manual generation on the ambiguous field was suppressing the automatic generation on it. Bug: 870220,852309 Change-Id: I6a3edd351e615289f6271fda5a45f6ff47e653af Reviewed-on: https://chromium-review.googlesource.com/c/1310713Reviewed-by:Vadym Doroshenko <dvadym@chromium.org> Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#605668}
Showing
This diff is collapsed.
Please register or sign in to comment