selenium: [🐛 Bug]: Lates Firefox browser version(v 102) is not support with selenium.

What happened?

When I try to run my selenium Test cases with the lates Firefox browser version (102), getting NS_Binding_Aborted (SessionNotCreated) Error.

When I trigger the test Browser opens and closed and getting the above error.

But when I run the test on downgraded Firefox browser (v101), tests are running successfully. So Im assuming Latest Firefox browser is not support with Selenium.

How can we reproduce the issue?

I'm unable to share any repo files since this is my office work related. Only way that you could reproduce, try to run a selenium C# with the lates gecko driver and the lates Firefox browser.

Relevant log output

System.InvalidOperationException: Error: NS_BINDING_ABORTED (SessionNotCreated)

Operating System

macOS

Selenium version

.Net 5.0

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

Firefox 102

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

Gecko driver 0.31.0.1

Are you using Selenium Grid?

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 18 (10 by maintainers)

Commits related to this issue

return to geckodriver, rm start-maximised, ref https://github.com/SeleniumHQ/selenium/issues/10840#issuecomment-1185358443 && https://bugzilla.mozilla.org/show_bug.cgi?id=1779723 — committed to joshhighet/ransomwatch by joshhighet 2 years ago

Most upvoted comments

Thanks for letting us know, @whimboo!

diemol on Jul 15, 2022

Note that Firefox doesn’t have a start-maximized command line argument but actually interprets it as the URL to open on startup (instead of about:blank). Internally start-maximized get completed to https://www.start-maximized.com/. This gets forward to some random page at least for me and then ends-up in a network error. Exactly this is what the NS_BINDING_ABORTED stands for.

As workaround remove start-maximized from the arguments and the problem will disappear.

For the underlying problem I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1779723 to get it fixed in Firefox.

I think that we can close this issue given that it’s not Selenium which misbehaves here.

whimboo on Jul 15, 2022