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

The element attributes obtained by rpa. windos are different from those obtained by the accessibility tool #1096

Open
CracktRoops opened this issue Sep 21, 2023 · 1 comment
Labels
bug Bad or unexpected behaviour help wanted Extra attention/deliberation/guidance is needed

Comments

@CracktRoops
Copy link

The rpa. windos scroll bar property is name: position and type: Thumb. After opening a window and closing it, the scroll bar property changes to name: position and type: CustomimControl. The type found using the element lookup tool is Thumb, and the code runtime found type: CustomimControl. What is the reason for this?

@cmin764
Copy link
Member

cmin764 commented Oct 26, 2023

Good question, can you post more details about it? Like:

  1. App name/binary (if not private)
  2. Tasks package code (former robot)
  3. What do you mean by "element lookup tool", is this Accessibility Insights? (or our helper tool windows-record)
  4. And by "code runtime", do you mean the printed logs by Print Tree?

Just in case the control type suddenly changes (and a better locator using name: / id: or class: strategies is not feasible), maybe it is worth trying an alternative one with the path: strategy.

@cmin764 cmin764 added bug Bad or unexpected behaviour help wanted Extra attention/deliberation/guidance is needed labels Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bad or unexpected behaviour help wanted Extra attention/deliberation/guidance is needed
Projects
None yet
Development

No branches or pull requests

2 participants