-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question]page.frame not referencing url in Chrome Dev Tools for Power BI report #3918
Comments
I apologize, I guess I don't know how to re-open and reference previous notes to new issue when commenting it doesn't solve my particular issue. Thanks for taking a look at that. I did do a playwright cli on that sight and the difference between that report and ours is this line. We don't have a view reference for our frame. This might have been required for them to make it public. const frame = page.frame({ url: 'https://app.powerbi.com/view**' }); My playwright is only returning the following when I click on the name which isn't working. // Click text="THERESA WADE" When I do this below I get the iframe name but unable to figure out how to reference the items in the rows |
Looks like a bug with the selector generation in playwright-cli. We'll be looking at frames as we do shadow dom there. Having a reduced test case would help! |
Let's address this in microsoft/playwright-cli#71. |
@pavelfeldman Didn't get a notification to see this before it was closed. What exactly are you looking for as a reduced test case? I can take the public Power BI report I referenced in my initial question and give you steps. Is this what you are looking for? |
Thanks for writing in, @wadezone. I'm not exactly sure if I understand the issue but I was able to use the website that you've shared to play with the app a bit and write a starter script using with Playwright.
I was able to click on the selector with
text="Weimei Corp
and do some actions on the right-click context menu. Are you thinking of building something like this? If you have a specific question, please feel free to re-open the issue.Originally posted by @arjun27 in #3915 (comment)
The text was updated successfully, but these errors were encountered: