-
Notifications
You must be signed in to change notification settings - Fork 305
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
PuppeteerRunnerExtension requirnig browser and page is cumbersome #201
Comments
Hey @steren, thanks for the feedback. Do you have a suggestion on how we could achieve this? |
I am not suggesting an implementation, I am suggesting an API surface. When I do Could the extension get its browser and page from the one used by |
Plus one to @steren comment. I think simplify this could further remove the barrier of entry, and help developers to make sense of the api (not everyone familiar with pptr browser) and getting started quicker. How about make the params optional? Supporting both: // use default setting, same as await createRunner(recording);
const runner = await createRunner(recording, new Extension());
// advance customization
const runner = await createRunner(recording, new Extension(browser, page, 7000) ); |
This comment was marked as off-topic.
This comment was marked as off-topic.
Also it would make more sense to pass the |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
For someone that is creating a new web browser as a beginner how do you suggest an API |
This module can simply be used by calling one method (
createRunner
), however, to customize the behavior, one needs to create anPuppeteerRunnerExtension
, and this one requires passingbrowser
andpage
.for simplicity, it would be better if an Extension would not requiring these, but would inherit the ones that I assume are created by
createRunner
Expected Behavior
Actual Behavior
The text was updated successfully, but these errors were encountered: