Workaround for strange Selenium behaviour#6431
Merged
Merged
Conversation
pablobm
force-pushed
the
selenium-workaround
branch
from
529cf34 to
b5d9662
Compare
Member
|
Looks good to me, thanks. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Extracted from #6424.
This is a workaround for Selenium/Webdriver throwing an error
You are trying to upload something that isn't a file, despite not trying to upload anything.In some circumstances, Selenium interprets the value
testin a form field as a placeholder for a fake file upload. No idea why. Hat tip to https://blog.konoson.com/webdrivererror-you-are-trying-to-upload-something-that-isnt-a-file for the info.This was discovered when trying to run a remote Selenium instance (in a separate Docker container). So I guess that's one such circumstance where this can happen.