summaryrefslogtreecommitdiffstats
path: root/chrome/browser/browsing_data_remover.h
diff options
context:
space:
mode:
authorjbauman@chromium.org <jbauman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-06-21 00:02:11 +0000
committerjbauman@chromium.org <jbauman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-06-21 00:02:11 +0000
commitc6d46bfd28e9669f4a8d70f804f7e6d230043287 (patch)
tree00be5f4141836b215a74376369ce12d2a0dc9523 /chrome/browser/browsing_data_remover.h
parentbae9c8381649cab153250d6df056a179080a1ffc (diff)
downloadchromium_src-c6d46bfd28e9669f4a8d70f804f7e6d230043287.zip
chromium_src-c6d46bfd28e9669f4a8d70f804f7e6d230043287.tar.gz
chromium_src-c6d46bfd28e9669f4a8d70f804f7e6d230043287.tar.bz2
Rely on losing focus, not on becoming unfullscreened, to destroy a fullscreen window.
On metacity we get spurious unfullscreen events that were preventing the window from going fullscreen, and alt-tab didn't cause the window to unfullscreen, so it wasn't destroyed by alt-tab. We should ignore the unfullscreen event and instead rely on FocusOut to determine when to destroy the window. BUG=117021 TEST= Review URL: https://chromiumcodereview.appspot.com/10542134 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@143306 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/browsing_data_remover.h')
0 files changed, 0 insertions, 0 deletions