Unable to interact with any element not currently visible since Dynamics Update
See original GitHub issueHi,
I’m running Dynamics 365 (9.1.0.5024) online with EasyRepro V9.1.0.1. We’ve recently begun experiencing an issue where we get errors when interacting with any elements which are not currently visible. We’ve discovered that a recent update of dynamics has introduced ‘lazy loading’ and the objects not currently visible therefore do not exist. Previously we were able to use a command such as :
Xrm.App.Entity.SetValue("title", "Example String");
Where ‘title’ is not currently visible and EasyRepro would navigate to this element and then continue the script.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
How I can avoid "Element is not currently visible and so ...
I have a sample code for selecting all mails in gmail.But the code throws an "Element is not currently visible and so may...
Read more >How to Solve ElementNotVisibleException in Selenium ...
First Solution: Try to write unique XPATH that matches with a single element only. Second Solution: Use Explicit wait feature of Selenium and ......
Read more >How to analyse 'Element not Found' exceptions when ...
So, first, check the visibility of spinner and then check for invisibility before interacting with other dynamic elements. 6. Now doubt your ...
Read more >Element Not Interactable Exception in Selenium
ElementNotInteractableException is an exception thrown by Selenium WebDriver when an element is present in the DOM, but it is not ...
Read more >How To Handle Element Not Interactable Exception - YouTube
Selenium WebDriver Element Not Interactable Exception is one of the most tricky to fix and it makes it a popular interview question.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@BenjaminDeveloper / @ryanpiran / @Bala-Ramadoss - I’ve been collaborating behind the scenes with Jason on this one. I have a meeting scheduled with our internal development team that introduced this change in behavior for the Unified Interface.
After my discussion with them we’ll determine the best path for fixing this in the long term. Thanks for your patience while we work to resolve this new rendering pattern with the Unified Interface.
My orgs just got updated and I can reproduce this - working on a fix.