summaryrefslogtreecommitdiffstats
path: root/webkit/glue
diff options
context:
space:
mode:
authorjcampan@chromium.org <jcampan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-03-27 23:29:45 +0000
committerjcampan@chromium.org <jcampan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-03-27 23:29:45 +0000
commit57346c5659ada3c2a06095afac6e53bedf41ab94 (patch)
tree59de8b6d58ce2a77445a7b4d57dd68eae986ddff /webkit/glue
parentb5f4e2c82f8443d62eaa21714822634de5cfbc46 (diff)
downloadchromium_src-57346c5659ada3c2a06095afac6e53bedf41ab94.zip
chromium_src-57346c5659ada3c2a06095afac6e53bedf41ab94.tar.gz
chromium_src-57346c5659ada3c2a06095afac6e53bedf41ab94.tar.bz2
The URL in the bug triggers an SSL interstitial for a redirect that redirects to a bad SSL page.
This happens because: - when proceeding on an interstitial, we wait for the navigation to commit before hiding the current interstitial - when showing an interstitial, if an interstitial is already showing we call DontProceed on it In the case of this bug, the interstitial has already been approved when the showing of the 2nd interstitial calls DontProceed on it, causing bad things to happen. The fix is easy: we shouldn't call DontProceed on an interstitial already "Proceeded". BUG=9286 TEST=See bug. Review URL: http://codereview.chromium.org/56019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12727 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit/glue')
0 files changed, 0 insertions, 0 deletions