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

som branch, bounding boxes on out-of-reach elements #41

Open
mlin12321 opened this issue Jun 23, 2024 · 1 comment
Open

som branch, bounding boxes on out-of-reach elements #41

mlin12321 opened this issue Jun 23, 2024 · 1 comment

Comments

@mlin12321
Copy link

mlin12321 commented Jun 23, 2024

For the som branch, some elements are visible to SeeAct via the html but not on the browser window (for instance, product categories being obscured by search results). However, bounding boxes are still attached to the obscured elements, causing SeeAct to believe it can click on elements that are not there. This can cause timeout issues, especially if SeeAct mistakes the bounding box on the obscured element for the elements on top of it (e.g. a search result covers a category tab, and SeeAct believes the bounding box for the category tab is for the search result).

@duz-sg
Copy link
Collaborator

duz-sg commented Jun 30, 2024

Did some searching and found this issue:
microsoft/playwright#9923
And yes, indeed it seems there is no way for us to tell, if there are two elements, one blocking another, which one is clickable. From playwright's point of view, they are both normal elements.

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

2 participants