feat(playwright): add PageAction extension point with built-in actions#1897
Open
feat(playwright): add PageAction extension point with built-in actions#1897
Conversation
Introduces a configurable post-navigate chain loaded from JSON via playwright.page.actions.config.file, so site-specific DOM transformations no longer require subclassing the protocol. Ships built-ins for overlay dismissal, clickable expansion, scroll-to-bottom, wait-for-selector, JS evaluation, and screenshot capture.
Contributor
|
This is great, reminds me of the NavigationFilter mechanism we have for Selenium. |
jnioche
approved these changes
May 5, 2026
Contributor
Author
Yes. It is inspired by it and we faced the lack of it in Playwright during Lisa's bachelor thesis :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduces a configurable post-navigate chain loaded from JSON via playwright.page.actions.config.file, so site-specific DOM transformations no longer require subclassing the protocol. Ships built-ins for overlay dismissal, clickable expansion, scroll-to-bottom, wait-for-selector, JS evaluation, and screenshot capture.