<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chrome on Selenium</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/tags/chrome/</link><description>Recent content in Chrome on Selenium</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 18 Sep 2025 10:46:23 +0200</lastBuildDate><atom:link href="https://deploy-preview-2575--selenium-dev.netlify.app/tags/chrome/index.xml" rel="self" type="application/rss+xml"/><item><title>A Curious Case of Selenium Manager Usage: What's Behind Chrome 127.0.6533.99?</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2025/selenium_manager_usage_whats_behind_chrome_127.0.6533.99/</link><pubDate>Sun, 14 Sep 2025 00:00:00 +0000</pubDate><guid>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2025/selenium_manager_usage_whats_behind_chrome_127.0.6533.99/</guid><description>&lt;p>Over the past two years, Selenium has included &lt;a href="https://www.selenium.dev/documentation/selenium_manager/">Selenium Manager&lt;/a>, a CLI tool (written in Rust) that provides &lt;strong>automatic management of drivers and browsers&lt;/strong> across all official language bindings (Java, JavaScript, Python, .NET, and Ruby). Its purpose is to simplify the developer experience: if you create a driver object like this:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-java" data-lang="java">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#000">WebDriver&lt;/span>&lt;span style="color:#f8f8f8;text-decoration:underline"> &lt;/span>&lt;span style="color:#000">driver&lt;/span>&lt;span style="color:#f8f8f8;text-decoration:underline"> &lt;/span>&lt;span style="color:#ce5c00;font-weight:bold">=&lt;/span>&lt;span style="color:#f8f8f8;text-decoration:underline"> &lt;/span>&lt;span style="color:#204a87;font-weight:bold">new&lt;/span>&lt;span style="color:#f8f8f8;text-decoration:underline"> &lt;/span>&lt;span style="color:#000">ChromeDriver&lt;/span>&lt;span style="color:#000;font-weight:bold">();&lt;/span>&lt;span style="color:#f8f8f8;text-decoration:underline">
&lt;/span>&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Selenium Manager takes care of detecting whether Chrome is installed, downloading the required driver, and even provisioning a copy of &lt;a href="https://googlechromelabs.github.io/chrome-for-testing/">Chrome for Testing (CfT)&lt;/a> if Chrome is not present on the system. This also works for Firefox and Edge, on Windows, Linux, and macOS.&lt;/p></description></item><item><title>Two Chrome features you should disable</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2024/chrome-browser-woes/</link><pubDate>Sun, 18 Aug 2024 00:00:00 +0000</pubDate><guid>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2024/chrome-browser-woes/</guid><description>&lt;h2 id="search-engine-selection-screen">Search engine selection screen&lt;/h2>
&lt;p>Starting with version 127 of Chrome, the browser &lt;a href="https://www.google.com/chrome/choicescreen/">now asks which search engine you would like to use&lt;/a>,
which is great for regular users.&lt;/p>
&lt;p>But for automation, it does so every single time.&lt;/p>
&lt;p>To bypass this, use the argument below when specifying the browser options.&lt;/p>
&lt;pre tabindex="0">&lt;code>--disable-search-engine-choice-screen
&lt;/code>&lt;/pre>&lt;h2 id="chrome-wastes-over-60mb-of-your-bandwidth-downloading-language-plugins">Chrome wastes over 60MB of your bandwidth downloading language plugins&lt;/h2>
&lt;p>The second feature is something that has been with Chrome for quite a while now.&lt;/p></description></item><item><title>What's new in Selenium Manager with Selenium 4.11.0</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2023/whats-new-in-selenium-manager-with-selenium-4.11.0/</link><pubDate>Mon, 31 Jul 2023 00:00:00 +0000</pubDate><guid>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2023/whats-new-in-selenium-manager-with-selenium-4.11.0/</guid><description>&lt;p>As of version &lt;a href="https://www.selenium.dev/blog/2022/introducing-selenium-manager/">4.6.0&lt;/a>, all releases of Selenium (Java, JavaScript, Python, Ruby, and .Net) are shipped with &lt;strong>Selenium Manager&lt;/strong>. &lt;a href="https://www.selenium.dev/documentation/selenium_manager/">Selenium Manager&lt;/a> is a binary tool (implemented in Rust) that provides automated driver management for Selenium. &lt;a href="https://www.selenium.dev/documentation/selenium_manager/">Selenium Manager&lt;/a> is still in beta, although it is becoming a relevant component of Selenium.&lt;/p>
&lt;p>So far, the main feature of Selenium Manager is called &lt;em>automated driver management&lt;/em>. I use the term &lt;em>management&lt;/em> for this feature (and not just &lt;em>download&lt;/em>) since this process is broader and implies different steps:&lt;/p></description></item><item><title>Dev and Beta Channel Browsers via Docker Selenium</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2022/dev-and-beta-channel-browsers-via-docker-selenium/</link><pubDate>Tue, 23 Aug 2022 00:00:00 +0000</pubDate><guid>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2022/dev-and-beta-channel-browsers-via-docker-selenium/</guid><description>&lt;p>The Docker Selenium browser Beta and Dev channel releases are now regularly published to &lt;a href="https://hub.docker.com/u/selenium">Docker Hub&lt;/a> and updated every two days. This enables testers and developers to test their applications on pre-release versions of Google Chrome, Mozilla Firefox, and Microsoft Edge before their official releases, using container tools, such as Docker. This empowers teams to stay ahead of the curve and catch potential showstoppers in their CI environment &lt;em>before&lt;/em> those issues have an impact on their users.&lt;/p></description></item></channel></rss>