8e97607389
There are two problems, exposed by existing tests: - We do not send Page.startScreeencast before Runtime.runIfWaitingForDebugger because we launch video recorder in between. This stalls when the page is busy immediately after resuming, e.g. with alert(). Fixed by starting video recorder in advance. - We wait for the first frame that may not come - for example, context-wide interception is blocking essential resource and first frame. Fixed by only waiting for the first frame before reporting the video, not the page. |
||
|---|---|---|
| .. | ||
| chromium.ts | ||
| crAccessibility.ts | ||
| crBrowser.ts | ||
| crConnection.ts | ||
| crCoverage.ts | ||
| crDevTools.ts | ||
| crExecutionContext.ts | ||
| crInput.ts | ||
| crNetworkManager.ts | ||
| crPage.ts | ||
| crPdf.ts | ||
| crProtocolHelper.ts | ||
| findChromiumChannel.ts | ||
| protocol.ts | ||
| videoRecorder.ts | ||