<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chromium on Selenium</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/tags/chromium/</link><description>Recent content in Chromium on Selenium</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 17 Oct 2023 16:14:50 +0200</lastBuildDate><atom:link href="https://deploy-preview-2575--selenium-dev.netlify.app/tags/chromium/index.xml" rel="self" type="application/rss+xml"/><item><title>Status of Selenium Manager in October 2023</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2023/status_of_selenium_manager_in_october_2023/</link><pubDate>Tue, 17 Oct 2023 00:00:00 +0000</pubDate><guid>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2023/status_of_selenium_manager_in_october_2023/</guid><description>&lt;p>Selenium Manager continues its development plan. As usual, in the latest releases, i.e., 0.4.13 and 0.4.14 (shipped with Selenium 4.13 and 4.14, respectively), we have fixed the problems reported so far. In these releases, the issues were related to the extraction of the Firefox binary from the self-extracting archive (SFX) in Windows and the advanced configuration through the configuration file (&lt;code>se-config.toml&lt;/code>) and environment variables (e.g., &lt;code>SE_BROWSER&lt;/code>). Moreover, these recent releases include new features, as explained below.&lt;/p></description></item></channel></rss>