Skip to content
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

Issue in scrolling up/down on the page in Dynamics 365 #631

Open
prachiwalke opened this issue Aug 19, 2019 · 4 comments
Open

Issue in scrolling up/down on the page in Dynamics 365 #631

prachiwalke opened this issue Aug 19, 2019 · 4 comments

Comments

@prachiwalke
Copy link

Can not find the element present at the far bottom or top of the page. It gives NoSuchElementException. Have to manually scroll up to that element while executing the Automation Script. Please help to solve this issue

@Haywaii
Copy link

Haywaii commented Aug 19, 2019

Can you provide more details here so people can help?
Like the code you use, which version of easyRepro, UCI or old interface?

It will be difficult for the community to help without having more information.

Thanks,

@ryanpiran
Copy link

@prachiwalke See issue #489 as this seems to be the same issue. A fix was released in the 9.1.0.5230 NuGet package. The issue was caused by the introduction of a 'lazy loading' feature released in a recent update of Dynamics. The fix introduced a new browser option called UCITestMode. When this option is set to True, the UCI app is in test mode. This test mode disables the lazy loading functionality that was introduced. The default behavior will be to set this value to True.

@mVermaat
Copy link
Contributor

mVermaat commented Aug 20, 2019

Yes the TestMode from issue #489 solves the fact that the page loads all elements. However, if the field is underneath the header (red area in image below), I do still get an error (Element Click Intercepted)

Secondary when the value is not in the view and it has to scroll up, it will scroll up making the field be in the red area too, causing an intercept.

Error

Edit: additional info

@vcinampudi
Copy link

Seems #631 and #623 are same

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants