question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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

See original GitHub issue

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?

no

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:18 (10 by maintainers)

github_iconTop GitHub Comments

1reaction
diemolcommented, Jul 15, 2022

Thanks for letting us know, @whimboo!

1reaction
whimboocommented, 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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Firefox 102 for developers - Mozilla - MDN Web Docs
This article provides information about the changes in Firefox 102 that will affect developers. Firefox 102 was released on June 28, 2022.
Read more >
Supported platforms — Firefox Source Docs documentation
This means that it does not yet offer full conformance with the WebDriver standard or complete compatibility with Selenium. You can track the...
Read more >
Firefox 102.0, See All New Features, Updates and Fixes
Various bug fixes and new policies have been implemented in the latest version of ... Firefox 102 is the new Extended Support Release...
Read more >
Which version of Firefox is compatible with Selenium?
I'm trying to run automated Python tests from the cmd prompt. Every time I try, I get an error message stating "Failed to...
Read more >
Security Vulnerabilities fixed in Firefox 102 - Mozilla
When a TLS Certificate error occurs on a domain protected by the HSTS header, the browser should not allow the user to bypass...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found