-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add use_resetter and wait_for_view kwargs #26
Open
mshriver
wants to merge
1
commit into
RedHatQE:master
Choose a base branch
from
mshriver:add-navigate-kwargs
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
@psav Thoughts? |
mshriver
force-pushed
the
add-navigate-kwargs
branch
from
January 16, 2019 16:00
d07ca46
to
68ca832
Compare
mshriver
commented
Jan 16, 2019
mshriver
force-pushed
the
add-navigate-kwargs
branch
2 times, most recently
from
January 16, 2019 16:09
dccd05b
to
d40c69e
Compare
mshriver
force-pushed
the
add-navigate-kwargs
branch
from
December 12, 2023 12:20
d40c69e
to
7be5abb
Compare
mshriver
force-pushed
the
add-navigate-kwargs
branch
from
December 12, 2023 12:24
7be5abb
to
279fbcf
Compare
mshriver
force-pushed
the
add-navigate-kwargs
branch
from
December 13, 2023 13:41
279fbcf
to
8c92ea3
Compare
mshriver
force-pushed
the
add-navigate-kwargs
branch
3 times, most recently
from
December 13, 2023 16:02
7ba15e1
to
e45ad9d
Compare
mshriver
force-pushed
the
add-navigate-kwargs
branch
from
December 13, 2023 16:05
0d389bc
to
adca211
Compare
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.
Next week I'll have the mental capacity to compare this with some hacks in iqe as im under the impression some passover is missing
I'd love to dig in Sooner but I do have to recover from the flu better first
mshriver
force-pushed
the
add-navigate-kwargs
branch
from
December 15, 2023 12:35
adca211
to
becbacd
Compare
control navigation via kwargs on navigate() use_resetter: Whether or not resetter function is called wait_for_view: timeout value for am_i_here to be true after post_navigate use_resetter defaults to True, current behavior maintained wait_for_view defaults to None, current behavior maintained Add NAVIGATE logging messages for both
mshriver
force-pushed
the
add-navigate-kwargs
branch
from
December 15, 2023 12:40
af2484f
to
c020287
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.
control navigation via kwargs on navigate()
use_resetter: Whether or not resetter function is called
wait_for_view: timeout value for am_i_here to be true after post_navigate
use_resetter defaults to True, current behavior maintained
wait_for_view defaults to None, current behavior maintained
FIXES #25