Schedule script evaluation for scripts enqueued by Page.addScriptToEvaluateOnNewDocument's source argument
Categories
(Remote Protocol :: CDP, enhancement, P2)
Tracking
(Not tracked)
People
(Reporter: impossibus, Unassigned)
References
(Blocks 5 open bugs)
Details
(Whiteboard: [puppeteer-beta2-mvp])
The content-document-global-created
observer notification looks relevant.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Scripts to execute will actually be hold within the frame tree instance of the current target. That said we need its implementation done, which I'm working on via bug 1605359 right now. Once that is done we can use the frameAttached
event to run all the registered scripts.
Comment 2•5 years ago
|
||
While Page.getFrameTree
gives us the list of already existent frames so that a script added later will be run in all frames, we also need Page.frameAttached
to call all the scripts when a new frame gets added. This can be done once bug 1599413 has been fixed.
Comment 3•5 years ago
|
||
Temporarily moving to Reserve Backlog as it is blocked on Bug 1599413 and to accommodate Bug 1599260 moving into the MVP Backlog.
Comment 4•5 years ago
|
||
As a side-node. When this gets implemented we will have to make sure that tests also check for the correct frameId
reported in the generated execution contexts, especially for a test which navigates to a frameset. I would like to defer those tests for now because without bug 1637640 been done, it is very hard to do.
Reporter | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Updated•2 years ago
|
Comment 5•2 years ago
|
||
Over on bug 1806413 we are getting this feature currently implemented for WebDriver BiDi.
Description
•