Incosistent behaviour of grabElementBoundingRect in iframe
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, node.js, playwright
- Domain
- testing-qa
Research direction
Start by reproducing the provided grabElementBoundingRect call inside an iframe with Playwright and WebDriver, comparing the returned coordinates. The issue is resolved when both integrations report iframe element positions consistently relative to the intended viewport.
Written by the indexing model from the issue text.
Description
What are you trying to achieve?
I have an iframe somewhere on my page, with some elements inside it. I am using grabElementBoundingRect to check if an element in the iframe is within the current viewport of the iframe (ie if i have to scroll down to see the element).
I am running my tests mostly with Playwright, but also with WebDriver on some platforms (hello, IE users!)
What do you get instead?
The values returned by grabElementBoundingRect on elements within iframes differ between these WebDriver and Playwright. Playwright returns an absolute x/y position on the screen, while WebDriver returns an x/y position within the iframe.
const elemRect = await within({frame: "#myIframe"}, () => {
return this.grabElementBoundingRect("#myElement");
});
Details
- CodeceptJS version: 3.0.4
- NodeJS Version: v14.15.4
- Operating System: Ubuntu 18.04
- Dominant language
- JavaScript
- Stars
- 4.2k
- Forks
- 756
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 16
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from codeceptjs/CodeceptJS
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
codeceptjs/CodeceptJS#5420 · 1 comment ·
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
codeceptjs/CodeceptJS#5358 · 1 comment ·
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
codeceptjs/CodeceptJS#4958 · 10 comments · 2 reactions ·
-
stale
Difficulty 1/5 Under an hour Newbie friendliness 72/100
codeceptjs/CodeceptJS#4778 · 3 comments ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 38/100
codeceptjs/CodeceptJS#5618 · 1 comment ·
All issues in codeceptjs/CodeceptJS
Similar issues
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Automattic/safe-publish#594 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
dream-num/dsh-univer-office#104 ·
-
comp/dashboard invalid P3
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NousResearch/hermes-agent#121143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
avniproject/avni-webapp#1811 ·
-
area/auroraboot area/webui bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100