Closed Bug 1733255 Opened 3 years ago Closed 3 years ago

"Page.lifecycleEvent" should only be emitted for top-level documents

Categories

(Remote Protocol :: CDP, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: whimboo, Assigned: whimboo)

References

Details

As given by the CDP documentation the Page.lifecycleEvent should only be emitted for top-level documents. Right now we do it also for each and every frame.

https://searchfox.org/mozilla-central/rev/b022ae1fc071ad7a29f64f281bc19b7b093df538/remote/cdp/domains/content/Page.jsm#281,350-355,361,368

emitLifecycleEvent() is called in _onFrameAttached() and handleEvent().

Going to work on that given it makes it easier for me to enable Fission for CDP browser-chrome tests over on bug 1601245.

Assignee: nobody → hskupin
Blocks: 1601245
Status: NEW → ASSIGNED

Hm, the documentation might actually be wrong. When I check the log output from Chrome as given on bug 1601245 comment 25 I can clearly see these events also being sent out for sub frames. As such I filed https://bugs.chromium.org/p/chromium/issues/detail?id=1254621 to get this clarified and fixed.

For now I'm assuming that it is an issue with the documentation and that events have to be sent out for all kinds of browsing contexts.

Closing out this bug given that it looks like a documentation error and we should better follow the actual behavior of Chrome.

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.