diff options
| author | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-06-30 21:41:25 +0000 |
|---|---|---|
| committer | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-06-30 21:41:25 +0000 |
| commit | 9ae7b9195f0e06b64664bba52e9cc0e8b3470f56 (patch) | |
| tree | c6cbd94204f2fb5fc8f758616b04feef455781a7 /ppapi/proxy/ppb_broker_proxy.cc | |
| parent | 48a96abb2464e6341d876c0a9c952764ce4a7a2e (diff) | |
| download | chromium_src-9ae7b9195f0e06b64664bba52e9cc0e8b3470f56.zip chromium_src-9ae7b9195f0e06b64664bba52e9cc0e8b3470f56.tar.gz chromium_src-9ae7b9195f0e06b64664bba52e9cc0e8b3470f56.tar.bz2 | |
ChromeFrame should report anchor navigations to Chrome. Currently this does not work as expected if
a navigation is first attempted to a ChromeFrame URL without the anchor followed by a navigation to
the same url with an anchor. In this case IE first sends an unload request to the currently loaded
CF document which causes a lot of grief as we run unload handlers on the page. The navigation never
proceeds to the new url though.
The proposed fix is to handle this in the onunload handler in CF by validating whether the new url
without the anchor is the same as the current url. If yes we just initiate a new navigation in Chrome.
Fixes bug http://code.google.com/p/chromium/issues/detail?id=85617
BUG=85617
Review URL: http://codereview.chromium.org/7290015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@91204 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ppapi/proxy/ppb_broker_proxy.cc')
0 files changed, 0 insertions, 0 deletions