Scroll elements into view before typing into element input #27905
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
islemaster
approved these changes
Apr 5, 2019
|
Very interesting. This does seem a little similar to an off-screen issue I worked around in a different way for iOS Safari UI tests: #27852 |
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.
On #27868, an unrelated PR, I'm seeing a consistent failure (locally and on drone) in
pd/regional_partner_mini_contact.feature: S3 logsThe failure is happening at steps where we are typing into text input elements, and it fails because the element is not "interactable".
Adding a step to scroll to the input element before typing into it fixes the problem on my end, although I'm still confused as to why this issue is only happening on my PR.