Closed
Bug 1553149
Opened 6 years ago
Closed 5 years ago
[meta] Page.frameStartedLoading
Categories
(Remote Protocol :: CDP, task)
Remote Protocol
CDP
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ato, Unassigned)
References
()
Details
(Keywords: meta, Whiteboard: [event=Page.frameStartedLoading])
No description provided.
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 1•6 years ago
|
||
Chrome emits this event, but neither Puppeteer nor the Gutenberg tests rely on it.
No longer blocks: puppeteer, puppeteer-mvp
Updated•5 years ago
|
Blocks: puppeteer-mvp
Updated•5 years ago
|
No longer blocks: puppeteer-mvp
Comment 2•5 years ago
|
||
In Puppeteer it's used inside the LifecycleWatcher
class, which seem to handle internal navigation state. Gutenberg e2e tests make use of embedded content which are iframes
. So I would say this is required for our alpha release.
Blocks: puppeteer, puppeteer-gutenberg
Whiteboard: [event=Page.frameStartedLoading] → [event=Page.frameStartedLoading][puppeteer-alpha]
Comment 3•5 years ago
|
||
The newly filed implementation bug 1597643 will cover the Gutenberg related work.
No longer blocks: puppeteer-gutenberg
Whiteboard: [event=Page.frameStartedLoading][puppeteer-alpha] → [event=Page.frameStartedLoading]
Comment 4•5 years ago
|
||
We now sent out this event with all the data as required. As such we no longer have to keep this meta bug open.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•4 years ago
|
Component: CDP: Page → CDP
You need to log in
before you can comment on or make changes to this bug.
Description
•