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
Looking at some code and i think this is incorrect, but it needs to be investigated with some working examples. frame is retrieved with h.ownerFrame, and later checked to see if frame != nil && frame.parentFrame != nil. In the if condition, the frame isn't used, instead h.frame. I would imagine that we should be working with the frame that was retrieved instead of h.frame.
Why?
This is confusing, and there are no comments or anything in the history to help us understand why we implemented it this way. Looking at Playwright, I can't find anywhere where they get the ownerFrame but then not use the result. This could be causing some unexpected incorrect behaviour when it comes to interacting with the website.
How?
We should:
Create test scripts and integration tests that use the checkHitTargetAt in ElementHandle.
Change the code so it works with frame instead of h.frame.
See if the change helps in any way.
Tasks
The content you are editing has changed. Please copy your edits and refresh the page.
What?
Looking at some code and i think this is incorrect, but it needs to be investigated with some working examples.
frame
is retrieved withh.ownerFrame
, and later checked to seeif frame != nil && frame.parentFrame != nil
. In the if condition, theframe
isn't used, insteadh.frame
. I would imagine that we should be working with theframe
that was retrieved instead ofh.frame
.Why?
This is confusing, and there are no comments or anything in the history to help us understand why we implemented it this way. Looking at Playwright, I can't find anywhere where they get the
ownerFrame
but then not use the result. This could be causing some unexpected incorrect behaviour when it comes to interacting with the website.How?
We should:
checkHitTargetAt
inElementHandle
.frame
instead ofh.frame
.Tasks
Tasks
Related PR(s)/Issue(s)
Could be related to the following issues:
The text was updated successfully, but these errors were encountered: