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.
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 waitForVisible() to all blocks #41126
Add waitForVisible() to all blocks #41126
Changes from 12 commits
7bf096d
85bfebf
db54e18
4432298
08435cb
65f3c62
1a00cd1
a5ba829
9dc1b8f
dd7aa72
0b2c965
46798af
36adacd
86a5d30
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Increasing the wait here before releasing the button press as found out that this is the culprit for flakiness on the
gutenberg-editor-block-insertion-2.test.js
tests.Some examples of this failing before the fix from the past week: 1, 2, 3.
This is how the test should look like when the wait time is enough and the correct element is pressed at the right time.
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.
Certain blocks don't return exactly one element (e.g. Column and Unsupported blocks), so updating the condition to as long as it's not 0.
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.
I think it would be interesting adding a parameter to the function to configure whether the function returns the first element or the elements array. It could be useful for those cases where we need to pick one of the elements, like for example in the
getLastBlockVisible
helper function.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.
Yeah I agree, since this always returns the first element, for cases like above, we have to make the call first before making a separate call to get the list of elements.
I'll make that enhancement in a separate PR, as might take a while to test to make sure it covers all use cases.