This fixes http://code.google.com/p/chromium/issues/detail?id=146&,

which was an issue with navigation attempts initiated by Flash not
working correctly in Chrome.

The plugin would initiate a navigation in response to a user click. This
would eventually result in a call to a script on the page, which would
query the history in a timer, and would end up resetting the selected
URL to the original URL as the history length would not be updated as
yet. The reason being the following:-

1. A Frame navigation is initiated by the renderer in response to the
user click.
2. This is sent as an async message to the browser UI thread.
3. When the navigation in the browser completes we update the history
info in render view asynchronously.

The fix is to attempt to update the history count when we receive notifications 
from webkit. These include notifications for items being added to the history,
navigations based on history (like history.back/forward/goto, etc).

These counts continue to be updated as before from the browser as well.

Added UI tests to test these cases.

Bug=146
R=jam


Review URL: http://codereview.chromium.org/7412

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@3457 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 3 insertions, 0 deletions

diff --git a/webkit/glue/webview_delegate.h b/webkit/glue/webview_delegate.h
index 4db62be..15e93ba 100644
--- a/webkit/glue/webview_delegate.h
+++ b/webkit/glue/webview_delegate.h
@@ -716,6 +716,9 @@ class WebViewDelegate : virtual public WebWidgetDelegate {
   // will occur.
   virtual void TransitionToCommittedForNewPage() { }
 
+  // Called when an item was added to the history
+  virtual void DidAddHistoryItem() { }
+
   WebViewDelegate() { }
   virtual ~WebViewDelegate() { }