diff options
| author | estade@chromium.org <estade@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-07-23 22:23:34 +0000 |
|---|---|---|
| committer | estade@chromium.org <estade@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-07-23 22:23:34 +0000 |
| commit | 04dd9d9de68e20da43e7e2f13a550ea7c8ca6fa3 (patch) | |
| tree | 829bef03332ca788797f63bd0407398e2c2cd800 /chrome/browser/gtk/browser_window_gtk.cc | |
| parent | 8a8c2cef05deb9e4fc6a9a271a06d9ef6ef49a7b (diff) | |
| download | chromium_src-04dd9d9de68e20da43e7e2f13a550ea7c8ca6fa3.zip chromium_src-04dd9d9de68e20da43e7e2f13a550ea7c8ca6fa3.tar.gz chromium_src-04dd9d9de68e20da43e7e2f13a550ea7c8ca6fa3.tar.bz2 | |
revert r53268:
------------------------------------
GTK: when closing a browser window, cancel the active drag session.
This speculatively works around an issue where users' windows would get stuck open in rare (non-reproducible, but widely reported) cases.
BUG=23733
TEST=none :(
-------------------------------------
I thought I had fixed the issue where dragging out the last tab closed the window. Apparently not.
BUG=50055
Review URL: http://codereview.chromium.org/3019024
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@53533 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/gtk/browser_window_gtk.cc')
| -rw-r--r-- | chrome/browser/gtk/browser_window_gtk.cc | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/chrome/browser/gtk/browser_window_gtk.cc b/chrome/browser/gtk/browser_window_gtk.cc index 4d8cf72..52f70e3 100644 --- a/chrome/browser/gtk/browser_window_gtk.cc +++ b/chrome/browser/gtk/browser_window_gtk.cc @@ -664,11 +664,6 @@ void BrowserWindowGtk::Close() { if (!window_) return; - // Sometimes the tabstrip will get stuck thinking it's in a drag session. - // Short of figuring out a repro case and actually solving the problem, this - // is the best way to avoid an immortal window. See http://crbug.com/23733 - tabstrip_->CancelActiveDragSession(); - if (!CanClose()) return; |