Dmitry Gozman cdb862767f fix(page): "load" event should fire before "waitForLoadState" resolves (#14897) ... 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.		2022-06-16 09:35:53 -07:00
..
har.ts	feat(route): fulfill with HARResponse (#14865)	2022-06-14 15:07:22 -07:00
harRecorder.ts	chore: use channels types instead of a copy in server (#14874)	2022-06-14 22:02:15 -07:00
harTracer.ts	fix(page): "load" event should fire before "waitForLoadState" resolves (#14897)	2022-06-16 09:35:53 -07:00