Skip to content
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

Add frames api #4

Closed
aslushnikov opened this issue Jun 14, 2017 · 0 comments
Closed

Add frames api #4

aslushnikov opened this issue Jun 14, 2017 · 0 comments
Assignees

Comments

@aslushnikov
Copy link
Contributor

There should be a frames inspection API with an ability to evaluate code in frame

aslushnikov added a commit that referenced this issue Jun 21, 2017
This patch implements FrameManager which is responsible for maintaining
the frame tree. FrameManager is quite basic: it sends FrameAttached,
FrameDetached and FrameNavigated events, and can report mainFrame and
all frames.

The next step would be moving certain Page API's to the Frame. For
example, such method as Page.evaluate, Page.navigate and others should
be available on Frame object as well.

References #4
pavelfeldman pushed a commit that referenced this issue Jun 21, 2017
This patch implements FrameManager which is responsible for maintaining
the frame tree. FrameManager is quite basic: it sends FrameAttached,
FrameDetached and FrameNavigated events, and can report mainFrame and
all frames.

The next step would be moving certain Page API's to the Frame. For
example, such method as Page.evaluate, Page.navigate and others should
be available on Frame object as well.

References #4
@aslushnikov aslushnikov added this to the Puppeteer: ready for dogfood milestone Jun 27, 2017
@aslushnikov aslushnikov self-assigned this Jun 27, 2017
aslushnikov added a commit that referenced this issue Jun 27, 2017
This patch implements Frame.evaluate method.

References #4.
aslushnikov pushed a commit that referenced this issue May 18, 2019
Fix `page.setContent` with unicode strings that exceeds the range of a 8-bit byte.

This patch implements decoding part of the [MDN's solution #4 for the "unicode problem"](https://developer.mozilla.org/en-US/docs/Web/API/WindowBase64/Base64_encoding_and_decoding#Solution_4_%E2%80%93_escaping_the_string_before_encoding_it).

Since we rely on node.js buffer to encode into base64, we don't have troubles with base64 encoding, so it is left as-is.

Fixes #4424
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant