You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is only possible to wrap instances with proxies upon creation. And since WebElement instances creation is incapsulated in the driver the above isn't possible.
The only workaround would be to intercept the driver's execute method as eventually all WebElement's method calls are routed there.
I face the same issue, The execute method is a protected method. It will not be intercepted by proxy. You can create a custom driver that extends the origin one. Override the execute method and make it public.
Do I have the most recent component updates?
Is the component officially supported by the Appium team?
Is there an existing issue for this?
Current Behavior
This issue is related to https://github.com/appium/java-client/blob/master/docs/The-event_firing.md .
The proxy method is not able to intercept click action, only driver based methods are intercepted
Expected Behavior
Please provide a fix or documentation on how to intercept webelement method calls
Minimal Reproducible Example
Environment
appium --version
):appium driver list
):appium plugin list
):node --version
):npm
version (output ofnpm --version
):Link to Appium Logs
No response
Further Information
No response
The text was updated successfully, but these errors were encountered: