What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If your Java project uses Selenium WebDriver BiDi and you are upgrading to Selenium 4.19 or later, update the imports for BiDi module classes: change org.openqa.selenium.bidi to org.openqa.selenium.bidi.module. Selenium says the APIs themselves stay the same; the documented migration is a source-level import change.
What changed in Selenium 4.19?
Selenium moved the listed Java BiDi module classes into the org.openqa.selenium.bidi.module package. Code using the old package path will need updated imports when compiled against Selenium 4.19 or later.
Before 4.19
import org.openqa.selenium.bidi.LogInspector;
import org.openqa.selenium.bidi.BrowsingContextInspector;
import org.openqa.selenium.bidi.Input;
import org.openqa.selenium.bidi.Script;
import org.openqa.selenium.bidi.Network;Selenium 4.19 and later
import org.openqa.selenium.bidi.module.LogInspector;
import org.openqa.selenium.bidi.module.BrowsingContextInspector;
import org.openqa.selenium.bidi.module.Input;
import org.openqa.selenium.bidi.module.Script;
import org.openqa.selenium.bidi.module.Network;These five examples come from Selenium’s Java BiDi import migration article. Search your Java source for org.openqa.selenium.bidi. imports and update affected module class paths. Then compile the project to identify any additional imports that need attention.
What does not need to change?
For the change described in Selenium’s migration article, the BiDi APIs remain as they are; the required adjustment is to import statements. You do not need to rewrite the calls to those APIs solely because of this package move.
Check the exact Selenium dependency version in your build file or lockfile before changing code. The migration boundary documented by Selenium is 4.19: versions before it use the old paths shown above, while 4.19 and later use the module package for the listed classes.
Why did Selenium move the classes?
Selenium says it was implementing W3C BiDi while working toward a future in which WebDriver Classic APIs could use BiDi APIs under the hood. During work on the BiDi browsingContext.locateNodes command, the project encountered a circular dependency in Bazel. It grouped BiDi classes for a module into a Bazel package and placed classes that call commands or events under a module package.
Rank #2
Selenium also notes that BiDi is under development, so protocol modules and APIs may be added or changed. The project says it strives to avoid breaking changes and to deprecate APIs for at least two versions before removal, but that this package change was difficult to handle through that approach.
How to troubleshoot the migration
- Compiler cannot find a BiDi class: Check whether its import still starts with
org.openqa.selenium.bidi.and whether the class belongs in themodulepackage. - The project still fails after changing the imports: Confirm the resolved Selenium Java version in the build file or lockfile, then compile again. This migration concerns Java package names; it does not establish that every browser and driver combination has identical BiDi support.
- You are unsure whether later BiDi changes apply: Separate this import migration from subsequent API additions and fixes. Review the changelog for the Selenium version actually resolved by your project rather than treating every later BiDi change as part of the 4.19 import edit.
What later Selenium releases tell you
The import move happened amid ongoing BiDi development, but later work should not be mistaken for the original migration requirement. Selenium’s Java changelog records a Bazel-file fix in 4.19.1. Its 4.19.0 notes also list BiDi additions, including storage and browser modules, network request and response commands, and an Input module command.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchSelenium’s February 20, 2026 announcement for 4.41 reports further Java BiDi work: JSpecify nullability coverage across BiDi packages and a JSON parsing fix for exponent-form numbers. These are later changes, not additional import instructions in the 4.19 migration article.
Which Selenium version is current?
On October 3, 2026, Selenium’s downloads page listed Java 4.49.0 as stable, released September 9, 2026, and 4.50.0-SNAPSHOT as a nightly build. Release listings change, so check the downloads page and your project’s resolved dependency when applying this guidance.
Rank #4
Or skip the browser setup
This Selenium change is about Java BiDi imports, not screenshot capture. If your separate task is to capture a webpage, ScreenshotNeo offers a one-request API:
Quick Recap
Best Value
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo documentation for request options. It removes cookie banners, popups and chat widgets before a shot; bot checks, blank pages and failed loads are never billed. Its MCP server lets AI agents take screenshots, and the free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Learn about ScreenshotNeo or sign up free.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
