Forum Discussion
Thank you, Alex!
I completely understand that situation and I'd be talking with the Architects and the designers. probably, we'll have to live with the way Angular JS controls work.
But, the good News is, I found another way to make it work and I was able to fetch the right row count and the required info from the table, and was able to get the size of it even when it's dynamic. I also came across some other facts with these type of controls which irritated me a lot. But after all that pain, it's working for me. Another thing with this type of control is, if you want to take some help from the DOM, even there it doesn't load all the rows at any given point in time. It displays the rows in the table on the UI dynamically based on how you scroll(up-down/left-right).
I used the Object.EvaluateXpath and to make the whole table load(doesn't happen unless you scroll back to the first item in the table) in the DOM and then calculate the size of it, I'm getting to the bottom of the table by using ScrollIntoViewIfNeed() on the first item(because I see the last/latest row when the table is displayed on the UI).
Thank you again for everyone's contribution to this thread.
Thank you
Abhi
Hi Abhi,
Thank you for the status update and hints provided.
In my case we also ended up with mostly using .EvaluateXpath() but, unfortunately, mostly searching for the displayed text.
There were already several threads on this forum where people struggled with Angular, so I think that others may benefit from the ways you have found to identify Angular controls on the page. Obviously, if they are not confidential, too implementation specific and may be shared.
Related Content
Recent Discussions
- 2 days agoGane195