af40eae13e
This changes the last actions, namely `click` and `press`, to not wait for the ongoing navigations after the action. Maintaining this behavior becomes tricky, because browsers move away from guaranteed synchronous navigations to optimized performance. See #34377 for more details. This is technically a breaking change. Most of the time, this should not be noticeable, because the next action will auto-wait the navigation and for any required conditions anyway. However, there are some patterns revealed by our tests that are affected: - Calling `goBack/goForward` immediately after an action. This pattern requires `expect(page).toHaveURL()` or a similar check inbetween. - Listening for network events during the action, and immediately asserting after the action. This pattern requires `waitForRequest()` or a similar promise-based waiter as recommended in best practices. We maintain the opt-out `env.PLAYWRIGHT_WAIT_AFTER_CLICK` that reverts to the old behavior for now. Additionally, previous opt-out option `env.PLAYWRIGHT_SKIP_NAVIGATION_CHECK` has been removed, because there have been just a single issue with it, that was immediately addressed in a patch release. |
||
|---|---|---|
| .. | ||
| bin | ||
| bundles | ||
| src | ||
| types | ||
| .eslintrc.js | ||
| .npmignore | ||
| browsers.json | ||
| cli.js | ||
| index.d.ts | ||
| index.js | ||
| index.mjs | ||
| package.json | ||
| README.md | ||
| ThirdPartyNotices.txt | ||
playwright-core
This package contains the no-browser flavor of Playwright.