Using any proximity selector in Taiko 1.4.3/1.4.4 throws TypeError: Cannot read properties of undefined (reading '1')

[sbehera1990]

Describe the bug
Using any proximity selector in Taiko 1.4.3/1.4.4 throws TypeError: Cannot read properties of undefined (reading '1')

To Reproduce
Steps (or script) to reproduce the behavior:
I am using gauge 1.6.14 and Taiko 1.4.3. The same code mentioned below used to work well with GUAGE1.5.7 and TAIKO 1.0.28.
After upgrading, it is throwing the above error TypeError: Cannot read properties of undefined (reading '1')
Create a step with any of the below code, it throws the above error.

assert.ok(await text(content1, toRightOf(content2)).exists());

or

assert.ok(await text(content1, toLeftOf(content2)).exists());

or

assert.ok(await text(content1, below(content2)).exists());

or

assert.ok(await text(content1, above(content2)).exists());

or

assert.ok(await text(expectedText, near(neighbourText)).exists());

Logs
26-08-2025 16:02:47.937 [Gauge] [ERROR] Stacktrace:
TypeError: Cannot read properties of undefined (reading '1')
at Object.getBoundingClientRect (node_modules\taiko\lib\handlers\domHandler.js:152:28)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async RelativeSearchElement.condition (node_modules\taiko\lib\taiko.js:2029:20)
at async RelativeSearchElement.validNodes (node_modules\taiko\lib\proximityElementSearch.js:65:11)
at async getMatchingNode (node_modules\taiko\lib\proximityElementSearch.js:30:28)
at async handleRelativeSearch (node_modules\taiko\lib\proximityElementSearch.js:13:25)
at async TextWrapper._get (node_modules\taiko\lib\elementWrapper\textWrapper.js:24:14)
at async node_modules\taiko\lib\elementSearch.js:358:22
at async waitUntil (node_modules\taiko\lib\helper.js:135:11)
at async node_modules\taiko\lib\elementSearch.js:356:7

Paste any log or error messages here

Expected behavior
All proximity selectors should work as expected.

Screenshots
Both the elements are getting highlighted as attached below, but not getting validated with the above code.

Versions:

• Taiko: 1.4.3
• Gauge 1.6.14
• OS Windows Server 2022 Standard
• Node.js 22.16.0

gauge -v
Gauge version: 1.6.14
Commit Hash: 9561cf7

Plugins
-------
html-report (4.3.3)
java (0.8.1)
js (5.0.1)
screenshot (0.3.2)

Additional context
Add any other context about the problem here.

[sbehera1990]

Can anyone please look into this issue and suggest some solution?

[zabil]

@sbehera1990 unfortunately, there isn’t much information to replicate this issue, making it difficult to understand the problem.

If you can share a sample project that replicates the issue, you’ll likely receive better support. Note that the sample project isn’t your current code; it’s a way to run, replicate, and debug the issue.

[sbehera1990]

Hi Zabil,

Thank you for responding.

On a sample project, though I am not getting the exact error above mentioned, it still fails at the step proximity selectors used.

Here is the link for the project https://github.com/sbehera1990/gauge-taiko-test/tree/master

[zabil]

@sbehera1990 thanks for the sample project i took the look. From the test it looks like it navigates to google tries to enter value and click on the button.

But the failure is valid because the screen does not have the search box and button ready yet as they pop up a privacy notice.

[sbehera1990]

@zabil I have only these 2 steps in my example.spec where I am only validating text, not entering any value in search box.

• Navigate to "https://www.google.com"
• Validate if page contains "Feeling Lucky" to right of "Google"

[Manikkumar1988]

@sbehera1990 From the test repo you shared, above is the error message Im getting.

If I change the word Google to Search, able to make the tests pass. Refer the below screenshot

What am I missing?

[sbehera1990]

Yes @Manikkumar1988, I also agree with the above solution to make the test run successfully.

It is purposefully added to validate the text with "Google" reference. With the unique text on the page, the tests run successfully. But the issue occurs when there are same text displayed multiple times on the page.

That is where I am facing issue with the latest Taiko version which used to go through successfully with Taiko 1.0.28.