[🐛 Bug]: Test using keyboard tabbing runs endlessly without failing (C# specflow, selenium 4.2.0)

What happened?

Since installing the package (selenium.webdriver net bindings for the SW API) I have a test which uses the below code to tab through a page of elements, since the update to 4.2.0 it no longer tabs beyond the first element on the page and it does not time out like other steps but stalls endlessly. If i go back to the previous version the step runs in a second with no issues.

When I use the "Tab" key on my keyboard to reach "Change Password" - **stalls here**
And I press "Enter"
And I am taken to the "Change Password" page

Apologies If i am missing something obviously I am relatively new to automation and coding and still trying to find my bearings.

How can we reproduce the issue?

Actions act = new Actions(driver);
            act.SendKeys(Keys.Tab);


            IWebElement elem = null;

            do
            {
                act.Perform();
                elem = driver.SwitchTo().ActiveElement();
                Debug.WriteLine("Text from an element: " + elem.Text);

            }
            while (!elem.Text.Contains(elementName));

        }

Relevant log output

no log output

Operating System

Windows 10

Selenium version

C#

What are the browser(s) and version(s) where you see this issue?

CHROME 102

What are the browser driver(s) and version(s) where you see this issue?

SELENIUM.WEBDRIIVER 4.2.0

Are you using Selenium Grid?

No response

[github-actions[bot]]

@Wanizame18, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

<div>

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

</div>

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.