diff options
| author | rafaelw@chromium.org <rafaelw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-05-19 20:26:25 +0000 |
|---|---|---|
| committer | rafaelw@chromium.org <rafaelw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-05-19 20:26:25 +0000 |
| commit | 5f362e0129c6f92953d1e772d72c07d9f0906ab2 (patch) | |
| tree | c180150b6f2808cbd61cc2a7cdab918e4f54e01c /webkit | |
| parent | a1a82d5215198f9ed128f6fc0b1f14cdf3034867 (diff) | |
| download | chromium_src-5f362e0129c6f92953d1e772d72c07d9f0906ab2.zip chromium_src-5f362e0129c6f92953d1e772d72c07d9f0906ab2.tar.gz chromium_src-5f362e0129c6f92953d1e772d72c07d9f0906ab2.tar.bz2 | |
fix chrome.tabs.onUpdated bugs, add browsertest.
This CL addresses a few issues related to the behavior of the onUpdated event.
Issue 1: The page re-entering the load state and the completing was causing multiple 'complete' status events to be fired. We now only report the first 'complete' after the didNavigate message is fired (iframe navigation, for example).
Issue 2: We were initializing the URL when the TabEntry was created, and this caused us to fail to send the url with the first navigation because we thought it wasn't changing.
BUG=27208,37149
Review URL: http://codereview.chromium.org/2111010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@47717 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit')
0 files changed, 0 insertions, 0 deletions