search

MarketSquare / robotframework-angularjs

An AngularJS and Angular extension to Robotframework's SeleniumLibrary
Apache License 2.0
34 stars 20 forks source link

Application with both angular and nonangular pages #38

Closed TestUserRobot closed 2 years ago

TestUserRobot commented 3 years ago

Clicking on a link in non-angular portal goes to angular pages.

Displays ' angular root element' error when clicking on link in non-angular. Tried even by separating keywords and settings in diff files.

emanlove commented 3 years ago

How are you using the AngularJSLibrary? Is the non-angular site the main site you start in?

You can turn off the implicit wait for angular call, which is producing the error as it is expecting an angualr website, either on the library import setting the ignore_implicit_angular_wait argument to ${True} or by using the Set Ignore Implicit Angular Wait keyword.

solomon2530 commented 3 years ago

What could be the solution if different pages of the same application show different root selectors?

emanlove commented 2 years ago

@solomon2530 There is currently not a solution for this. I assume if this is required, a keyword could be created to set the root element instead of just initializing it on library import.

As this is an old issue without any activity I am closing it. If the requirement for being able to change root selector by keyword still remains feel free to open a new ticket.