-
Notifications
You must be signed in to change notification settings - Fork 41
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
Fix navigate to link in new page #1334
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We have identified that the call to RunIfWaitingForDebugger wasn't being performed at the correct time when a new page was created after a link was clicked on that opened the page. The first step is to move out of the initOptions so that we can eventually run it independently of the other setup/init steps.
ankur22
force-pushed
the
fix/827-link-new-window
branch
from
May 15, 2024 13:37
dbe0a49
to
1d00ce3
Compare
ankur22
force-pushed
the
fix/827-link-new-window
branch
from
May 15, 2024 13:39
1d00ce3
to
cde4f4f
Compare
ankur22
changed the title
Refactor RunIfWaitingForDebugger
Fix navigate to link in new page
May 15, 2024
inancgumus
reviewed
May 15, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice fix and test :) A few suggestions.
inancgumus
approved these changes
May 15, 2024
This test ensures that a new page is opened and correctly navigated to when a link with target=_blank is clicked on.
Instead of basing the test on waiting a certain time and retrying every so often, we're now working with the built in APIs that help with this wait action in a more stable manner.
ankur22
force-pushed
the
fix/827-link-new-window
branch
from
May 15, 2024 15:11
6ed6d20
to
56dc610
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Move the CDP request
RunIfWaitingForDebugger
to be called first when creating aFrameSession
.Why?
We have identified that the call to
RunIfWaitingForDebugger
wasn't being performed at the correct time when a new page was created after a link was clicked on that opened the page.This is currently the simplest and safest solution. I tried to place some of the CDP actions that are in
NewFrameSession
within their own goroutines but there were data races.Checklist
Related PR(s)/Issue(s)
Updates: #827