summaryrefslogtreecommitdiffstats
path: root/chrome/browser/autocomplete
diff options
context:
space:
mode:
authorbrettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-09-01 16:03:48 +0000
committerbrettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-09-01 16:03:48 +0000
commit371cc8b150c13f3ddc1c8e23d8d879f836f02e2f (patch)
tree244fad88cf99b6b0ed9b8275c31712f1b7b27150 /chrome/browser/autocomplete
parent28e94c09ff48b3200306b06a28c03e9d9faa6ec7 (diff)
downloadchromium_src-371cc8b150c13f3ddc1c8e23d8d879f836f02e2f.zip
chromium_src-371cc8b150c13f3ddc1c8e23d8d879f836f02e2f.tar.gz
chromium_src-371cc8b150c13f3ddc1c8e23d8d879f836f02e2f.tar.bz2
When finding the navigation entry for updating the title, we should use the
site instance from the RVH that is updating the title rather than the current one. The current one might be a different process, which has a different page_id namespace and could cause us to get confused. If we get the page ID from the renderer, we should use the SiteInstance from the same one rather than getting it from somewhere else. I don't know exactly what case this might happen in, I just noticed this big via inspection when looking at the code. TEST=none BUG=none Review URL: http://codereview.chromium.org/3228007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58179 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/autocomplete')
0 files changed, 0 insertions, 0 deletions