thunderstrike/puppeteer
thunderstrike/puppeteer
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
2,924 Commits 2 Branches 0 Tags 31 MiB
cfaaa5e2c0
Commit Graph

6 Commits

Author SHA1 Message Date
Alex Rudenko
2a0eefb99f
fix: handle service workers in extensions (#8807) 
Closes #8800
 2022-08-17 19:34:34 +02:00
jrandolf
bdcb748b98
chore: infrastructure for injecting scripts into DOMWorlds (#8801) 2022-08-17 14:39:41 +02:00
Alex Rudenko
3fad05d333
fix: custom sessions should not emit targetcreated events (#8788) 
Closes #8787
 2022-08-16 10:56:13 +00:00
Alex Rudenko
8cb5043868
fix: resolve target manager init if no existing targets detected (#8748) 
Closes #8747
 2022-08-06 15:35:42 +02:00
Alex Rudenko
49193cbf1c
fix: specify the target filter in setDiscoverTargets (#8742) 
To stay compatible with the next version of Chromium.
See https://chromedevtools.github.io/devtools-protocol/tot/Target/#method-setDiscoverTargets
 2022-08-04 11:46:53 +00:00
Alex Rudenko
2cbfdeb0ca feat: use CDP's auto-attach mechanism (#8520) 
* feat: use CDP's auto-attach mechanism

In this PR, we refactor Puppeteer to make use of the CDP's auto-attach mechanism. This allows the backend to pause
new targets and give Puppeteer a chance to configure them properly. This fixes the flakiness related to dealing with
OOPIFs and should fix some other issues related to the network interception and navigations. If those are not fixed completely by this PR, the PR serves a solid base for fixing them.

Closes https://github.com/puppeteer/puppeteer/issues/8507, https://github.com/puppeteer/puppeteer/issues/7990
Unlocks https://github.com/puppeteer/puppeteer/issues/3667

BREAKING CHANGE: With Chromium, Puppeteer will now attach to page/iframe targets immediately to allow reliable configuration of targets.
 2022-08-02 13:18:07 +00:00