Selenium News and Updates: A Smattering of Selenium 106
A look back at Selenium’s July 2012 roundup, what its links covered, and how to separate that archive from today’s Selenium release information.
“A Smattering of Selenium #106” is a historical Selenium roundup by Adam Goucher, published on July 31, 2012. It covered Marionette and FirefoxDriver, FlynnID and Android devices on Grid, a Geb tutorial, and a Proxy & Executor talk. It is an archive item, not a current Selenium news issue; “Selenium 106” here does not mean Selenium version 106. SeleniumHQ’s release page lists Selenium 4.50.0, released September 30, 2026, as latest at the research timestamp. ScreenshotNeo is a website screenshot API and MCP server that can help developers capture pages while investigating browser behavior.
What “A Smattering of Selenium #106” refers to
The number is the issue number of a blog roundup. The post’s original opening line was: “In case you are curious, the train just went past my old neighbourhood.” — Adam Goucher. The links and descriptions belong to the post’s 2012 context; they should not be read as present-day feature or compatibility guidance.
The four topics in the 2012 roundup
Marionette and FirefoxDriver
The post described Marionette as “the future of the Firefox driver.” That is a characterization from 2012, not a current status statement about Firefox automation. For current Selenium release details, consult the direct release record and the package page for the binding you use.
FlynnID, Android devices, and Grid
The roundup noted that a FlynnID 0.2 configuration-format change was relevant to attaching Android devices to Grid. This does not establish current Android or Grid compatibility. Before reviving an old setup, verify the device, browser, driver, Selenium version, and Grid configuration against current documentation.
Geb and the Page Object pattern
The post linked a tutorial about Geb, a Groovy browser-automation tool, and its use of the Page Object pattern. The durable takeaway is architectural: page objects can keep selectors and page interactions together, while tests describe user-facing behavior. The old link is historical context, not a recommendation about current library versions.
Proxy & Executor
Goucher mentioned a talk he had given in San Francisco, San Jose, and Toronto, linking slides, video, and notes. This was a report about the talk and its resources, not a Selenium release announcement.
How to read the archive alongside current Selenium news
- Identify the date and author. This is Adam Goucher’s July 31, 2012 post.
- Keep its claims time-bound. Marionette, FlynnID, Android-on-Grid, and Geb references describe what the post linked or said then. Check current documentation before using them to make an implementation decision.
- Check release sources directly. At the research timestamp, SeleniumHQ’s GitHub release record identifies 4.50.0 (September 30, 2026) as latest, while the official downloads page still lists 4.49.0 as stable across core bindings and Grid. That discrepancy means you should verify your language package’s published version before updating.
- Keep the immediately prior release in context. The official Selenium 4.49 announcement is dated September 9, 2026, and covers JavaScript, Ruby, Python, .NET, Java, and Grid. It is useful release-cadence background, but 4.49.0 is not the latest according to the direct 4.50.0 release record at the timestamp above.
The 4.50.0 release notes list WebDriver BiDi work across bindings, relative locator support in Java and .NET, and other fixes. Release records and package publication can become available at different times, so check the specific binding package before pinning an upgrade.
Trying Selenium Grid today
The current official getting-started guide lists Java 11 or higher, an installed browser, and browser drivers as prerequisites. Selenium Manager can configure drivers automatically. For a basic standalone setup, start the Selenium Server JAR and point RemoteWebDriver tests to http://localhost:4444. Follow the official Grid getting-started guide for current download and launch instructions, since commands depend on the server artifact and environment.
Do not use the 2012 FlynnID note as a current recipe for attaching Android devices. Confirm the current Grid node setup and compatibility for your target device and browser first.
Capture a page while investigating browser behavior
A screenshot can make a browser automation failure easier to inspect: capture the page after navigation, after an interaction, or at the point where the test fails. With a local Selenium session, use the screenshot API provided by your language binding and save the returned bytes to a file. The exact method varies by binding and driver; consult the current Selenium API documentation for your language.
For a remote screenshot of a public page, ScreenshotNeo accepts one GET request with a URL and returns PNG, JPEG, WebP, or PDF. Its request options include viewport and device presets, full-page capture, waiting, custom headers and cookies, and caching. See the ScreenshotNeo API documentation for parameter details.
Or skip the browser setup
Use ScreenshotNeo when you need a clean capture of a page without configuring a browser or driver. Cookie banners, newsletter popups, and chat widgets are removed before the shot; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);Read the API docs, then sign up for 1,000 free screenshots a month with no card.
Troubleshooting current-release checks
| Symptom | Likely cause | What to do |
|---|---|---|
| The downloads page and release page show different versions. | The pages may reflect different publication or stability states. | Use the direct release record to identify the newest release, then check your language’s package page before upgrading. |
| An old Grid or Android example does not work. | The 2012 roundup only recorded a historical configuration note; it does not guarantee current compatibility. | Start with the current Grid guide and verify each browser, driver, device, and node configuration. |
| A Selenium Manager setup cannot find a browser. | The Grid guide still requires an installed browser; managing a driver does not install the browser itself. | Install a supported browser, then follow the current Grid setup guide and inspect the server logs. |
| A screenshot misses content or captures an intermediate state. | The page may render asynchronously, lazy-load content, or show a transient overlay. | In a browser test, wait for the relevant condition before capturing. With a screenshot API, configure a selector wait or other supported wait option. |
Performance, reliability, and cost considerations
- Release reliability: pin a known package version in CI and upgrade deliberately. Check the binding’s published version rather than assuming every release page updates simultaneously.
- Grid reliability: ensure the browser is installed and the server is reachable at the configured endpoint. Selenium Manager can help with driver setup, but the Grid guide lists the browser as a separate prerequisite.
- Capture performance: full-page captures and waits for slow pages naturally take longer than a viewport capture. Capture only the page state or region needed for diagnosis when speed matters.
- ScreenshotNeo costs: Free is 1,000 shots/month; Starter is $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000. Yearly billing gives two months free. Every feature is available on every plan.
FAQ
Is Selenium 106 a Selenium version?
No. In this title, 106 is the issue number of a 2012 blog roundup.
Does the post prove Marionette is the current Firefox driver?
No. It records how the project was characterized in July 2012. Check current Selenium and browser documentation for present-day guidance.
Which Selenium version should I install?
At the research timestamp, the GitHub release page listed 4.50.0 as latest, while the downloads page listed 4.49.0 as stable. Verify the version published for your language binding before changing your dependency.
Can ScreenshotNeo replace Selenium in an automated test?
It is a screenshot API and MCP server, useful for capturing pages without setting up a browser for that capture. It does not make this historical roundup a current Selenium test guide.
Sources
- A Smattering of Selenium #106 — Adam Goucher, July 31, 2012.
- Selenium 4.50.0 release record.
- Official Selenium downloads.
- Grid getting started.
- Selenium 4.49 announcement.
