Andrey Lushnikov
Andrey Lushnikov
As of puppeteer v1.7.0, a workaround would be to use raw devtools protocol: ```js const session = await page.target().createCDPSession(); await session.send('Network.enable'); const cert = await session.send('Network.getCertificate', {origin: 'https://example.com'}); console.log(cert); ```
This would require some work in DevTools protocol, but should be doable. This is low-pri for us unless it proves to have high demand.
@mcpine9 please upvote the issue itself - we sort by upvotes when figuring what to do next
Clicking extension buttons should enable other testing scenarios, e.g. "tab capture" API requires user gesture: https://github.com/GoogleChrome/puppeteer/issues/2229
Upstream has landed as [r496577](https://chromium.googlesource.com/chromium/src.git/+/1168352b7fc90f83f71ae014f0d97f6ce7402786), we now need to roll.
@nisrulz additional work is required upstream, we're working on it.
@pavelfeldman r590913 is not enough for a complete story; I'm working on `Page.FileDownloaded` event to notify about successful download.
@dheerajbhaskar so there are two jobs in one: > get the new page object Tip-of-tree puppeteer has a new [`'popup'`](https://pptr.dev/#?product=Puppeteer&version=master&show=api-event-popup) event specifically to address this. > wait for the new...
For the record: @allada has an upstream patch for this: https://chromium-review.googlesource.com/c/chromium/src/+/740401
@gdamjan it is merged. We're waiting on a network layer servicification to complete in Chromium before relying on the functionality.