cdb862767f
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. |
||
|---|---|---|
| .. | ||
| callMetadata.ts | ||
| channels.ts | ||
| DEPS.list | ||
| protocol.yml | ||
| serializers.ts | ||
| transport.ts | ||
| validator.ts | ||
| validatorPrimitives.ts | ||