Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] Firefox & Webkit not getting locator inside frame

See original GitHub issue

Context:

Playwright Version: 1.21.1
Operating System: Windows
Node.js version: 16.13.0
Browser: Firefox & Webkit

Code Snippet

const frameLocator = this.page.frameLocator('[id="card-number-element"] iframe');
const locator = frameLocator.locator('input[type=text][name=cardnumber]');
await locator.fill('some text'); // Fails ONLY in FIREFOX & WEBKIT

Describe the bug I have a test case in which I work with elements inside frames, and the test works in Chromium but not in Firefox or Webkit

When doing await page.frameLocator(frameSelector).locator(frameElementSelector).fill() (or any other action) it works in Chromium but not in Firefox Firefox getting next error: With the trace on this is the information I get from it:

Action was interrupted
locator.fill
TIME
wall time: 04/05/2022, 17:43:19
duration: Timed Out
PARAMETERS
selector: "[id="card-number-element"] iframe >> control=enter-frame >> input[type=text][name=cardnumber]"
strict: true
value: "4000 0000 0000 0002"
LOG
waiting for frame "[id="card-number-element"] iframe"
selector resolved to visible <iframe scrolling="no" frameborder="0" allowtransparency…></iframe>
waiting for selector "[id="card-number-element"] iframe >> control=enter-frame >> input[type=text][name=cardnumber]"

Issue Analytics

State:
Created a year ago
Comments:9 (7 by maintainers)

Top GitHub Comments

1reaction

kachkaevcommented, Aug 3, 2022

Thanks for your reply @dgozman! I tried crafting more or less reliable repro steps in https://github.com/blockprotocol/blockprotocol/pull/483 but failed so far. CI fails after adding --repeat-each 100 and focusing on just one test case. However, I can’t reproduce a trace in which I’ve see an input in a mini-screenshot, but a failed frame.locator("input").

This situation happened locally a couple of times, but the repro case was not reliable enough. I’ll keep watching CI results and update you here if I have any new findings.

Thanks again for your attention on this mystery! Playwright is awesome! 😍

0reactions

dgozmancommented, Aug 2, 2022

@kachkaev Perhaps there is a bug in snapshot code that we would be happy to debug. How can I run this test locally to reproduce the issue?