[Bug]: Issues with iframes

[karolwajs]

Version

1.49.0

Steps to reproduce

After upgrade to the newest chromium headless version my tests started to fail when i'm trying to access/make actions on some iframe elements, which isn't the case on the lower versions. I switched one of the click methods to dispatchEvent('click') and i see that this way it's working. I can't provide any specific example reproduction steps besides of mui date picker: https://mui.com/x/react-date-pickers/date-picker/, which is constantly failing in my case.

It's happening for very different locators, so i cannot provide any specific locator methods or actions, which will trigger this behaviour. I would be grateful for help, because that's the thing which is working for us on previous playwright and browser versions, it started to happen when we tried to switch to the newest one.

Channel: 'chromium'

Expected behavior

I expect iframes to work like in previous versions

Actual behavior

Error: Timed out 20000ms waiting for expect(locator).toBeVisible()

Locator: locator('.gldbm-panel__dbmIframe').contentFrame().getByTestId('extras')
Expected: visible
Received: <element(s) not found>
Call log:
  - expect.toBeVisible with timeout 20000ms
  - waiting for locator('.gldbm-panel__dbmIframe').contentFrame().getByTestId('extras')

Additional context

No response

Environment

System:
    OS: macOS 15.1
    CPU: (8) arm64 Apple M2
    Memory: 99.83 MB / 16.00 GB
  Binaries:
    Node: 20.12.1 - ~/.nvm/versions/node/v20.12.1/bin/node
    npm: 10.5.0 - ~/.nvm/versions/node/v20.12.1/bin/npm
  Languages:
    Bash: 3.2.57 - /bin/bash
  npmPackages:
    @playwright/test: ^1.49.0 => 1.49.0

[dgozman]

@karolwajs Thank you for the issue! It seems like there is a difference in how new and old headless handle these iframes. However, it's unlikely we can fix the issue without a repro. Anything that shows the problem, even if not consistently, would be a great help.

[karolwajs]

If you click 'book now', the iframe will be opened (page.frameLocator('.gldbm-panel__dbmIframe')) with the booking engine, every interaction with a calendar (when it's displayed), clicking on dates for example won't be executed properly on v1.49.0 version

[dgozman]

@karolwajs Unfortunately, clicking "Booking now" does not open any iframe for me. But even then, guessing the actions that do not work is not something that I'd like to do. Could you please record a short script on that page that does work without channel: 'chromium' and does not work with the channel specified?

[karolwajs]

'Book now', not 'Booking now'. Every action taken on the opened calendar is not working with channel 'chromium'

Example script:

import date from 'date-and-time';
import { type FrameLocator, type Locator, type Page } from '@playwright/test';

test(
  'iFrame Test',
  async ({ page }) => {
    const startDate = new Date();
    const formattedStartDate = date.format(startDate, 'dddd, MMMM D, YYYY');
    await page.goto('https://gxpservicesstagestorage.z6.web.core.windows.net');
    await page.getByText('Book Now').click(); 
    await page.frameLocator('.gldbm-panel__dbmIframe').locator('#gldbm_startdate').click();
    await page.frameLocator('.gldbm-panel__dbmIframe').getByLabel(`Choose ${formattedStartDate} as your check-in date. It’s available.`).click();
 });

The last click won't be executed. (code will be executed, but the click won't happen).
It will work with .dispatchEvent('click')

[mxschmitt]

When I try to run your script, the site is hanging after I click on "Book Now" - looks like the site doesn't work for me?

[karolwajs]

It should work now

[mxschmitt]

What do you mean with "click won't happen"? I tried to create a smaller script which shows on the screenshot that the click happens. The screenshot it seems that the "Check in" is updated to the selected date:

import { chromium } from 'playwright';

(async () => {
  const browser = await chromium.launch({
    channel: 'chromium',
    // headless: false,
  });
  const context = await browser.newContext({
    viewport: {
      width: 1920,
      height: 1080
    }
  });
  const page = await context.newPage();

  await page.goto('https://gxpservicesstagestorage.z6.web.core.windows.net');
  await page.getByText('Book Now').click();
  await page.frameLocator('.gldbm-panel__dbmIframe').locator('#gldbm_startdate').click();
  await page.frameLocator('.gldbm-panel__dbmIframe').getByLabel(`Choose Friday, November 29, 2024 as your check-in date. It’s available.`).click();
  await page.waitForTimeout(5000)
  await page.screenshot({ path: 'screenshot.png' });
  console.log('written screenshot');
  await browser.close();
})();

[karolwajs]

When i switched viewport settings to:
viewport: {
width: 1920,
height: 1080
}
it seems to work fine, weird that it worked for different viewport settings previously. I have to check rest of the suite, because i believe that i had similar issues with some other components on this page