[Password Manager] Suppress UI when password generation is active

components/autofill/content/renderer/autofill_agent.h

Index: components/autofill/content/renderer/autofill_agent.h
diff --git a/components/autofill/content/renderer/autofill_agent.h b/components/autofill/content/renderer/autofill_agent.h
index c75d5d6f443a51555e923adf712f5de57a76ed2a..c71f31d4bbcd22ee47cbe119e593ecbbbb7d06ac 100644
--- a/components/autofill/content/renderer/autofill_agent.h
+++ b/components/autofill/content/renderer/autofill_agent.h
@@ -266,6 +266,12 @@ class AutofillAgent : public content::RenderFrameObserver,
   // messages to close the Autofill popup when it can't possibly be showing.
   bool is_popup_possibly_visible_;
 
+  // If the generation popup is possibly visible. This is tracked to prevent
+  // generation UI from displaying at the same time as password manager UI.
+  // This is needed because generation is shown on field focus vs. field click
+  // for the password manager. TODO(gcasto): Have both UIs show on focus.

[Ilya Sherman, 2015/06/16 02:24:09]

Long-term, should there be a combined UI?  Or are we sure that the generation
popup should always trump the password autofill popup?

[Garrett Casto, 2015/06/16 06:15:05]

Really only one of these should be active at any time. If the password field is
for a new password, then we should only show generation, if it's for a current
password we should only show the password management UI. At the moment there are
going to be cases where both trigger because heuristics aren't perfect, but it's
quite rare since we generally don't show the password manager UI when the
password field is focused. 

With increased support for change password forms this conflict may start
happening more often. It's possible that we will need some way to disambiguate, 
we'll just have to see how often it happens.

[Ilya Sherman, 2015/06/16 19:49:23]

Should we record some metrics to verify whether this is indeed common or rare?

[Garrett Casto, 2015/06/17 19:48:10]

I added something in the latest patch. Even if this ends up showing a large
amount of conflicts, I'm not totally sure what we would do about it since we
don't know for certain which is correct, but in all cases I know of now
generation is the right UI if they are in conflict.

+  bool is_generation_popup_possibly_visible_;
+
   base::WeakPtrFactory<AutofillAgent> weak_ptr_factory_;
 
   DISALLOW_COPY_AND_ASSIGN(AutofillAgent);