-
Notifications
You must be signed in to change notification settings - Fork 188
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
Using 'Displayed' leads to WebDriverException on 4.0.0.2-beta #263
Comments
This happens because the original ,net Selenium lib intercepts some API calls in W3C mode (inlcuding isDisplayed) and replaces them with CC @akinsolb |
@mykola-mokhnach Going to fix this today by applying a JSONWP command for IsElementDisplayed. |
I mean this is not the only endpoint, that might be affected: |
@mykola-mokhnach Can I be sure that the same endpoints apply to the .Net version? |
I cannot say for sure. It is just for your information and depends on the actual W3C implementation by the .net client |
There aren't any tests for this yet. I'll find out sooner or later. @lanzelot1989 I'll publish a new beta today. |
fix for #263 to override Selenium Displayed endpoint call
@akinsolb: Thanks for the quick feedback. Maybe there is a related problem, please tell me if I should enter it separately: This sound like it is something similar to what @mykola-mokhnach described. |
@lanzelot1989 please raise a separate issue for the 'The Driver.FindElementByClassName' problem |
@akinsolb as requested, I created appium-dotnet-driver#265 |
Description
When using Appium.WebDriver 4.0.0.2-beta the Displayed property throws a WebDriverException.
Environment
Details
Using the Displayed property throws the exceptions below with 4.0.0.2-beta, this still worked with 4.0.0.1-beta. The Enabled property works as excepted.
Used package versions:
Code To Reproduce Issue [ Good To Have ]
Exception stacktraces
Link to Appium logs
The text was updated successfully, but these errors were encountered: