Reading issue
← Back to microsoft/playwright
microsoft / playwright · Issue No. 42850
1.63.0
import { test } from '@playwright/test'
test('frame highlight', async ({ page }) => {
await page.setContent(
'<iframe name="frame" srcdoc="<button>foo</button>"></iframe><button>bar</button>',
)
const locator = page.frame('frame')!.locator('button')
await locator.highlight() // incorrectly highlights the "bar" button outside the frame
await locator.click() // correctly clicks the "foo" button inside the frame
})
the button inside the frame is highlighted
the button outside the frame is highlighted
possibly related: #42849
System:
OS: Windows 11 10.0.22631
CPU: (12) x64 11th Gen Intel(R) Core(TM) i5-11500H @ 2.90GHz
Memory: 9.94 GB / 31.20 GB
Binaries:
Node: 26.3.1 - C:\Users\user\AppData\Roaming\node\node.EXE
npm: 11.16.0 - C:\Users\user\AppData\Roaming\node\npm.CMD
IDEs:
VSCode: 1.134.0 - C:\Users\user\AppData\Local\Programs\Microsoft VS Code\bin\code.CMD
npmPackages:
@playwright/test: 1.63.0 => 1.63.0
playwright-core: ^1.43.0 => 1.63.0
Relay reads this issue against the repository's contribution signals: the files it is likely to touch, how the maintainers triage work this size, and what the first contribution would exercise.
The full analysis for this issue is still being assembled. Until then, the description above and the thread on GitHub are the most reliable context.