From 8ebf9d7699ce8fec1593e33641c2bc65db38443a Mon Sep 17 00:00:00 2001 From: Yury Semikhatsky Date: Tue, 16 Aug 2022 15:31:30 -0700 Subject: [PATCH] test: disable page/page-set-content.spec.ts:126 in webkit (#16596) The test started failing on WebKit after WebKit/WebKit@7de67f9 The cause is the same as in other browsers - missing utility context. Disabling the test in WebKit similar to the other browsers in order to prepare for the next webkit roll. Related: #16536 --- tests/page/page-set-content.spec.ts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/page/page-set-content.spec.ts b/tests/page/page-set-content.spec.ts index 2d8d87a511..4f0c903bfc 100644 --- a/tests/page/page-set-content.spec.ts +++ b/tests/page/page-set-content.spec.ts @@ -123,8 +123,8 @@ it('content() should throw nice error during navigation', async ({ page, server } }); -it('should return empty content there is no iframe src', async ({ page, browserName }) => { - it.fixme(browserName === 'firefox' || browserName === 'chromium', 'Hangs in FF && CR because there is no utility context'); +it('should return empty content there is no iframe src', async ({ page }) => { + it.fixme(true, 'Hangs in all browsers because there is no utility context'); await page.setContent(``); expect(page.frames().length).toBe(2); expect(await page.frames()[1].content()).toBe('');