You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
barjin opened this issue
May 31, 2024
· 2 comments
· Fixed by #2542
Assignees
Labels
featureIssues that represent new features or improvements to existing features.t-toolingIssues with this label are in the ownership of the tooling team.
Following the recent update adding the shadow root expansion to the parseWithCheerio method, it would be nice if we could expand iframe elements (their contents) in a similar manner.
While replacing the iframe element in a browser could cause some styling / security issues, I'm assuming it's just a simple XML tree modification for Cheerio.
The text was updated successfully, but these errors were encountered:
barjin
added
feature
Issues that represent new features or improvements to existing features.
t-tooling
Issues with this label are in the ownership of the tooling team.
labels
May 31, 2024
Looks like unless explicitly allowed, we cant access the content of an iframe from another origin at all. I was trying to get the HTML from inside the iframe of giscus comments and you only get null from the iframe.contentDocument in there.
You're talking about DOM API, right? I think there should be some way to look into the iframes from the Playwright orchestration (at least the docs say so).
featureIssues that represent new features or improvements to existing features.t-toolingIssues with this label are in the ownership of the tooling team.
Following the recent update adding the shadow root expansion to the
parseWithCheerio
method, it would be nice if we could expandiframe
elements (their contents) in a similar manner.While replacing the
iframe
element in a browser could cause some styling / security issues, I'm assuming it's just a simple XML tree modification for Cheerio.The text was updated successfully, but these errors were encountered: