Index: chrome/browser/ui/exclusive_access/flash_fullscreen_interactive_browsertest.cc |
diff --git a/chrome/browser/ui/exclusive_access/flash_fullscreen_interactive_browsertest.cc b/chrome/browser/ui/exclusive_access/flash_fullscreen_interactive_browsertest.cc |
index 6dbd08c128a3fbd4525a76b416cbe2dbdedeef0d..7102b0e0ce9f11f6cb006018c83e974bebfe68e6 100644 |
--- a/chrome/browser/ui/exclusive_access/flash_fullscreen_interactive_browsertest.cc |
+++ b/chrome/browser/ui/exclusive_access/flash_fullscreen_interactive_browsertest.cc |
@@ -270,8 +270,10 @@ IN_PROC_BROWSER_TEST_F(FlashFullscreenInteractiveBrowserTest, |
// stored/restored correctly. Mouse and keyboard events are used to confirm |
// that the widget the UI thinks is focused is the one that responds to these |
// input events. |
+// |
+// Flaky, see http://crbug.com/444476 |
IN_PROC_BROWSER_TEST_F(FlashFullscreenInteractiveBrowserTest, |
- FullscreenWithinTab_FocusWhenSwitchingTabs) { |
+ DISABLED_FullscreenWithinTab_FocusWhenSwitchingTabs) { |
ASSERT_TRUE(ui_test_utils::BringBrowserWindowToFront(browser())); |
StartFakingTabCapture(); |
ASSERT_TRUE(LaunchFlashFullscreen()); |