Closed OrKoN closed 2 months ago
The test from https://github.com/puppeteer/puppeteer/pull/12677/files
const {server, page, puppeteer, browser} = state; await page.goto(server.EMPTY_PAGE); const frame1Promise = page.waitForFrame(frame => { return page.frames().indexOf(frame) === 1; }); const frame2Promise = page.waitForFrame(frame => { return page.frames().indexOf(frame) === 2; }); await attachFrame( page, 'frame1', server.CROSS_PROCESS_PREFIX + '/frames/one-frame.html' ); await Promise.all([frame1Promise, frame2Promise]); const dump1 = await dumpFrames(page.mainFrame()); using browserTwo = await puppeteer.connect({ browserWSEndpoint: browser.wsEndpoint(), protocol: browser.protocol, }); const pages = await browserTwo.pages(); const emptyPages = pages.filter(page => { return page.url() === server.EMPTY_PAGE; }); expect(emptyPages.length).toBe(1); const dump2 = await dumpFrames(emptyPages[0]!.mainFrame()); expect(dump1).toEqual(dump2);
it looks like chromium-bidi does not recover out-of-process iframes on reconnect.
cc @sadym-chromium
@sadym-chromium Should this be closed?
fixed by https://github.com/GoogleChromeLabs/chromium-bidi/pull/2381
The test from https://github.com/puppeteer/puppeteer/pull/12677/files
it looks like chromium-bidi does not recover out-of-process iframes on reconnect.