Dmitry Gozman e942138913 fix: do not report errored pages after context closure (#4346) ... Consider the following sequence: - page opens a popup; - popup target is attached, we start initializing it; - user calls browser.close(); - browser is closed, and popup initialization fails; - we report "errored page" on the already closed context; - RPC client cannot make sense of this: "Cannot find parent object BrowserContext@guid to create Frame@guid" This issue was revealed during Firefox pipe migration.		2020-11-04 16:23:38 -08:00
..
client	api(videos): introduce a single recordVideo option bag (#4309)	2020-11-02 19:42:05 -08:00
debug	feat(har): allow saving har for context (#4214)	2020-10-26 14:32:07 -07:00
dispatchers	feat(scopes): make page a scope (#4300)	2020-11-02 13:06:54 -08:00
install	fix(env): respect =true/false as env values for boolean flags (#4228)	2020-10-23 12:44:12 -07:00
protocol	fix(har): support har in persistent context (#4322)	2020-11-03 11:30:59 -08:00
server	fix: do not report errored pages after context closure (#4346)	2020-11-04 16:23:38 -08:00
trace	chore: cleanup some har code (#4306)	2020-11-02 13:38:55 -08:00
utils	feat(scopes): make page a scope (#4300)	2020-11-02 13:06:54 -08:00
.eslintrc.js	chore(lint): add @typescript-eslint/type-annotation-spacing rule (#897)	2020-02-07 13:36:49 -08:00
browserServerImpl.ts	api(videos): introduce a single recordVideo option bag (#4309)	2020-11-02 19:42:05 -08:00
driver.ts	feat(har): allow saving har for context (#4214)	2020-10-26 14:32:07 -07:00
inprocess.ts	feat(har): allow saving har for context (#4214)	2020-10-26 14:32:07 -07:00