PK

This can also happen on `2.6.1`, if one container was stopped or recreated, it's impossible to sync them again.

Hetzner Cloud

I was able to receive and extract push notifications from the browser, but not in headless mode - #3432 My use case is logging the notifications from several pages.

Is this expected behavior? Any help is appreciated.

@aslushnikov I'm sorry, forgot that in my example but used it in my code. I hope this helps: ``` const puppeteer = require('puppeteer'); (async() => { const browser = await...

I think my previous results aren't accurate because I wasn't able to receive notifications again with the 'push' permission (I've also upgraded to 1.10.0). I did some more testing: Normal...

@aslushnikov do you think you could add push and (better?) SW coverage in the near future? If not, is it possible to handle the push notifications with the dev protocol?

"is it possible to handle the push notifications with the dev protocol?" 🤔

"notifications" is for normal notifications it seems while the "push" permission is for push notifications: https://pptr.dev/#?product=Puppeteer&version=v1.10.0&show=api-browsercontextoverridepermissionsorigin-permissions But it's not working - related to #3432

Got the same problem, a custom middleware for Vite helped: ``` function crossOriginIsolationMiddleware(_, response, next) { response.setHeader("Cross-Origin-Opener-Policy", "same-origin"); response.setHeader("Cross-Origin-Embedder-Policy", "require-corp"); response.setHeader("Cross-Origin-Resource-Policy", "cross-origin"); next(); } const crossOriginIsolation = { name: 'cross-origin-isolation',...