Adding Mouse Support for new GTK Autofill

chrome/renderer/autofill/autofill_agent.h

Index: chrome/renderer/autofill/autofill_agent.h
diff --git a/chrome/renderer/autofill/autofill_agent.h b/chrome/renderer/autofill/autofill_agent.h
index 85ea7e64dc98853d67c6c9ee09c4549194d63cd1..b95c1ee6dbeb2064ed20599a74ae161378b58766 100644
--- a/chrome/renderer/autofill/autofill_agent.h
+++ b/chrome/renderer/autofill/autofill_agent.h
@@ -105,6 +105,10 @@ class AutofillAgent : public content::RenderViewObserver,
 
   // For external Autofill selection.
   void OnSelectAutofillSuggestionAtIndex(int listIndex);
+  void OnSetAutofillActionFill();

[csharp, 2012/01/26 22:19:06]

These functions all just use the currently set autofill_query_element_, is that
accepted or should we be explicitly telling this code which element to work on?
If we go that way do you know if it is possible to get the original web node
from the FormField? (I did a bit of searching and it looks like that isn't
possible right now)

[Ilya Sherman, 2012/01/30 22:11:09]

Yeah, that should be fine.  We've generally also used autofill_query_id_ to
ignore out of date responses, so the autofill_query_element_ should always be
the "right" element.
Nope, there's no way that I'm aware of to map from a FormField to the original
web node.  We could pass the raw node pointer to the browser process and pass it
back to the renderer; but that's a little unpleasant, because the raw pointer
does not point to anything meaningful within the browser process.

+  void OnSetAutofillActionPreview();
+  void OnClearForm();
+  void OnSetNodeText(string16 value);
 
   // Called in a posted task by textFieldDidChange() to work-around a WebKit bug
   // http://bugs.webkit.org/show_bug.cgi?id=16976