You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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.
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).
The text was updated successfully, but these errors were encountered: