Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: implement improved waitForNavigation #11929

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jrandolf
Copy link
Contributor

@jrandolf jrandolf commented Feb 15, 2024

This PR implements a waitForNavigation that doesn't validate the expected flow and instead only cares about results.

  • It will wait for a response if it can.
  • It will wait for the first navigation (fragment or not).
  • It will wait for the completion condition (if available).
  • It will wait for other conditions when navigation is not fragment navigation.

This also modifies the bidi/core API to match the BiDi spec as defined.

@jrandolf jrandolf requested a review from OrKoN February 15, 2024 20:22
@jrandolf jrandolf force-pushed the jrandolf/update-wait-for-navigation branch from 9f305e6 to dd7f2d5 Compare February 15, 2024 20:25
@jrandolf
Copy link
Contributor Author

@OrKoN This PR is expected to fail btw. That's because the navigationStarted event is incorrect. I'm working on a fix in Chromium BiDi.

@jrandolf jrandolf force-pushed the jrandolf/update-wait-for-navigation branch from dd7f2d5 to c37cb8f Compare February 16, 2024 10:37
@OrKoN OrKoN force-pushed the jrandolf/update-wait-for-navigation branch from c37cb8f to c658b83 Compare February 16, 2024 11:24
@OrKoN
Copy link
Collaborator

OrKoN commented Feb 16, 2024

@jrandolf thanks, after a quick review, it looks good. I will give it another review once it is ready to be landed.

@jrandolf jrandolf force-pushed the jrandolf/update-wait-for-navigation branch from c658b83 to fe4cc01 Compare February 19, 2024 12:34
@OrKoN OrKoN force-pushed the jrandolf/update-wait-for-navigation branch from fe4cc01 to a468c73 Compare February 28, 2024 15:25
@OrKoN
Copy link
Collaborator

OrKoN commented Feb 28, 2024

@jrandolf how complicates is a fix or a work-around for chromium-bidi? it looks like the current implementation has additional flakiness as described in https://bugzilla.mozilla.org/show_bug.cgi?id=1882454 (responseCompleted coming after load)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants