Dekel Barzilay

v10.2.0 broke the `page.setRequestInterception(true)` flow for me and probably for all the puppeteer plugins that are using it. I reverted to v10.1.0, where it still works. The `page.on('request', request =>...

[Issue](https://github.com/puppeteer/puppeteer/issues/7475#issuecomment-927993338) still reproduces consistently on my end with puppeteer v13.0.1 while working fine when reverted back to v10.1.0 It's probably got something to do with the [puppeteer-extra](https://github.com/berstend/puppeteer-extra) module and its...

I've noticed that `page.setRequestInterception(true)` is working fine in the latest puppeteer version when I'm removing the usage of `enchant-puppeteer` module, which is meant to provide a workaround when you need...

I agree, though it seems to require adding specific support for it in puppeteer-extra plugins, which I was trying to avoid. I guess I would have to fork these plugins...

Awesome, thanks!

I've just published a [new library](https://www.npmjs.com/package/feathers-http-distributed) to distribute FeathersJS apps over the network with inter-service communication using HTTP protocol. The [feathers-http-distributed](https://www.npmjs.com/package/feathers-http-distributed) module was built as preparation for migrating all our...

For me the issue happens in non-headless mode, so I'm not sure how it works in the headless mode. I haven't seen an issue with `fixPluginArray`, but since both `fixIframeContentWindow`...

Hi @bslayton, I have no idea, but Maybe @mdmitry01 can answer this one.

@avimar If you think this behavior should be changed, you can always open a PR with a short description to explain its need.

@avimar, Please check the following issues regarding model's virtual attributes that do not return in the response: - https://github.com/feathersjs-ecosystem/feathers-objection/issues/117 - https://github.com/feathersjs-ecosystem/feathers-objection/issues/45