disable SitePerProcessBrowserTest.NestedFrameViewportIntersectionUpdated on android
It is flaky.
TBR=kenrb@chromium.org
Bug: 869758
Change-Id: I6ac4db8ae505c3b40a3b3ce486833b82a0737ad9
Reviewed-on: https://chromium-review.googlesource.com/1158583
Reviewed-by: Christos Froussios <cfroussios@chromium.org>
Commit-Queue: Christos Froussios <cfroussios@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579799}diff --git a/content/browser/site_per_process_browsertest.cc b/content/browser/site_per_process_browsertest.cc
index 57ccbda..bfb6b40 100644
--- a/content/browser/site_per_process_browsertest.cc
+++ b/content/browser/site_per_process_browsertest.cc
@@ -12055,8 +12055,16 @@
// Test to verify that viewport intersection is propagated to nested OOPIFs
// even when a parent OOPIF has been throttled.
+// TODO(crbug.com/869758) The test is flaky on android
+#if defined(OS_ANDROID)
+#define MAYBE_NestedFrameViewportIntersectionUpdated \
+ DISABLED_NestedFrameViewportIntersectionUpdated
+#else
+#define MAYBE_NestedFrameViewportIntersectionUpdated \
+ NestedFrameViewportIntersectionUpdated
+#endif
IN_PROC_BROWSER_TEST_F(SitePerProcessBrowserTest,
- NestedFrameViewportIntersectionUpdated) {
+ MAYBE_NestedFrameViewportIntersectionUpdated) {
GURL main_url(embedded_test_server()->GetURL(
"foo.com", "/frame_tree/scrollable_page_with_positioned_frame.html"));
EXPECT_TRUE(NavigateToURL(shell(), main_url));
