Open Bug 1603776 Opened 5 years ago Updated 1 year ago

[meta] Page.navigate returns too early

Categories

(Remote Protocol :: CDP, task)

task

Tracking

(Not tracked)

People

(Reporter: whimboo, Unassigned)

References

(Depends on 1 open bug, Blocks 2 open bugs)

Details

(Keywords: meta)

There are several situations when Page.navigate returns too early and this is visible eg. when doing full screenshots which show a lot of placeholders for images. Or Network.getCookies doesn't return any cookie.

David, I think that we should take this into account for Q1.

Depends on: 1593340
Blocks: 1604723
Blocks: 1610454
Depends on: 1618863
Component: CDP: Page → CDP
Severity: normal → S3

Any progress on this bug recently?

It makes CDP unusable in lot of cases including mine.

Is there any other way to make sure page is loaded after navigation?

Sorry but there isn't any update and most likely wont. We do not actively work on CDP anymore given that it is in maintenance mode. We still accept patches for sure but the problem here is probably larger and related to bug 1706353, which is barely solvable with the current architecture.

Instead we focus on WebDriver BiDi which Puppeteer already partly supports. Not sure which client you are using but maybe you have a chance to change the underlying protocol already?

We use CDP using Selenium C#.

I thought BiDi is based on CDP so that it's almost the same thing?

No, both are different protocols and BiDi is officially a spec and works / will work cross-browser. So wait until Selenium let you use the Bidi endpoints for navigation and it should all work fine. If you have further question feel free to drop into https://chat.mozilla.org/#/room/#webdriver:mozilla.org and ask your questions. We are happy to help.

You need to log in before you can comment on or make changes to this bug.