Currently, `loadstate` and `load` are two separate events in the protocol, and are fired in this order. As a result, `waitForLoadState()` sometimes resolves before the `'load'` event is fired, which is unexpected. Also fixes a flaky test that assumed `load` event comes after `domcontentloaded` for the empty page, which is not always a case in Chromium. |
||
|---|---|---|
| .. | ||
| android | ||
| assets | ||
| components | ||
| config | ||
| electron | ||
| installation | ||
| library | ||
| page | ||
| playwright-test | ||
| stress | ||
| index.d.ts | ||
| tsconfig.json | ||