Fix DoubleClick, ContextClick in the UI Recorder #1786
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
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.
If right now someone is using the defaul UI Recorder that is in the Releases page, they will get lots of warning for every single DoubleClick or ContextClick function (Double-click and Right-click).
The warning looks the following:
'RemoteWebDriver.Mouse' is obsolete: 'This property was never intended to be used in user code. Use the Actions or ActionBuilder class to send direct mouse input.'With Actions there is no warning and now we are not using Coordinates to perform these two actions, which should also produce less errors and misses for people who use UI Recorder Tool.