Closed Bug 1597259 Opened 5 years ago Closed 5 years ago

Implement Page.setLifecycleEventsEnabled

Categories

(Remote Protocol :: CDP, task, P1)

task

Tracking

(firefox72 fixed)

RESOLVED FIXED
Firefox 72
Tracking Status
firefox72 --- fixed

People

(Reporter: whimboo, Assigned: whimboo)

References

()

Details

(Whiteboard: [puppeteer-alpha])

Attachments

(1 file)

To be able to send Page.lifecycleEvents (bug 1597253) those have to be turned on first. This method accepts a boolean to turn it on or off.

Blocks: 1549483
No longer blocks: puppeteer

Don’t we already implement Page.setLifecycleEventsEnabled as a no-op,
meaning it’s really Page.lifecycleEvent we’re missing?

Not sure what you mean, but the no-op doesn't turn on the events. This still has to be implemented for this method.

I was pointing to the fact that in other cases where we have
similar enable/disable toggles, we have closed the meta bugs because
there’s no additional work left on them specifically: the implementation
work that needs to happen is with the events.

We closed those because internally we set a flag for the current state. That's not what we did here, and as such the implementation is not complete.

Pushed by hskupin@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1e9d52a8c4b7 [remote] Implement Page.setLifecycleEventsEnabled. r=remote-protocol-reviewers,maja_zf
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 72
Component: CDP: Page → CDP
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: