Dmitry Gozman

@tui95 Thank you for the issue, this is indeed the case.

@Nickheythatsme Thank you for interest in contributing to Playwright! This issue might not have an easy fix, because we rely on the `expect` library to produce the diff message. Unless...

@bgotink Thank you for the feature request! I understand your usecase, but I don't think we are going to change how CSS selectors work. - Recursing into `slot` children is...

> While the "Don't click me!" button technically exists, it is invisible and unreachable. I agree that it is confusing if you look at the rendered page. However, fallback content...

> In my code I'm performing actions along the line of "click the confirm button in the footer", which no longer work if the button is placed in the footer...

@qk5 In scenarios similar to yours, we recommend to use `Locator`s to identify the frame element. You can convert `Locator` to `FrameLocator` at any moment - see "Converting Locator to...

After discussing with the team, it seems like the best solution would be to introduce `Locator` `FrameLocator` conversions, something like `Locator.enterFrame()` and `FrameLocator.exitFrame()`. This way you can always call `Locator`...

This looks the same as #28476. @pasieronen could you please try `@playwright/test@next` to see whether that's already fixed for you?

Small repro that shows one page clicking, and another page stalling. It looks like clicks in different contexts do not happen in parallel. ```mjs import { firefox } from '@playwright/test';...

> @dgozman Do I understand correctly that the problem was fixed in version 1.43? Yes, the fix has been released in v1.43.