<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Release Policy on DotNetBrowser Docs</title><link>https://teamdev.com/dotnetbrowser/releases/</link><description>Recent content in Release Policy on DotNetBrowser Docs</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 18 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://teamdev.com/dotnetbrowser/releases/index.xml" rel="self" type="application/rss+xml"/><item><title>DotNetBrowser 3.5.0</title><link>https://teamdev.com/dotnetbrowser/releases/2026/v3-5-0/</link><pubDate>Wed, 18 Feb 2026 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2026/v3-5-0/</guid><description>&lt;h2 id="added-new-initialization-exceptions" data-title>
Added new initialization exceptions&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#added-new-initialization-exceptions
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>New exception classes have been introduced to cover various engine initialization failure scenarios:&lt;/p>
&lt;ul>
&lt;li>&lt;code>SandboxNotSupportedException&lt;/code> - Thrown when Chromium can&amp;rsquo;t launch in the sandboxed mode, because, the environment doesn&amp;rsquo;t support creating processes within a new user namespace.&lt;/li>
&lt;li>&lt;code>UserDataInUseException&lt;/code> - Thrown when another Chromium instance is already using the same user data directory.&lt;/li>
&lt;li>&lt;code>UserDataCreationException&lt;/code> - Thrown when the user data directory cannot be created due to insufficient permissions or an invalid directory path.&lt;/li>
&lt;/ul>
&lt;p>All new exceptions inherit from &lt;code>EngineInitializationException&lt;/code>, ensuring existing code continues to work while enabling type-safe exception handling.&lt;/p></description></item><item><title>DotNetBrowser 3.4.0</title><link>https://teamdev.com/dotnetbrowser/releases/2026/v3-4-0/</link><pubDate>Wed, 21 Jan 2026 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2026/v3-4-0/</guid><description>&lt;h2 id="sandbox-on-linux" data-title>
Sandbox on Linux&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#sandbox-on-linux
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>In DotNetBrowser 3.4.0, the Chromium sandbox is now enabled on Linux. This sandbox is a crucial security feature that has
already been available on Windows and macOS.&lt;/p>
&lt;h3 id="action-required" data-title>
Action required&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#action-required
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Chromium relies on &lt;a href="https://man7.org/linux/man-pages/man7/namespaces.7.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>user namespaces&lt;/a> to sandbox subprocesses.
When this feature is unavailable, DotNetBrowser cannot start Chromium and throws a &lt;code>EngineInitializationException&lt;/code>
during &lt;code>IEngine&lt;/code> initialization.&lt;/p></description></item><item><title>DotNetBrowser 3.3.7</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-7/</link><pubDate>Thu, 18 Dec 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-7/</guid><description>&lt;h2 id="net-10-support" data-title>
.NET 10 support&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#net-10-support
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>DotNetBrowser is tested and proven to integrate with .NET 10 desktop applications.&lt;/p>
&lt;h2 id="chromium-1430749941" data-title>
Chromium 143.0.7499.41&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1430749941
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces 13 security fixes. Among them:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-13630"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-13630: Type Confusion in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-13631"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-13631: Inappropriate implementation in Google Updater&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-13632"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-13632: Inappropriate implementation in DevTools&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-13633"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-13633: Use after free in Digital Credentials&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the Chromium &lt;a href="https://chromereleases.googleblog.com/2025/12/stable-channel-update-for-desktop.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>blog post&lt;/a>.&lt;/p></description></item><item><title>DotNetBrowser 2.27.20</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-20/</link><pubDate>Wed, 26 Nov 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-20/</guid><description>&lt;h2 id="chromium-14207444176" data-title>
Chromium 142.0.7444.176&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-14207444176
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces important security fixes. Among them:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/cve-2025-13042"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-13042: Inappropriate implementation in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/cve-2025-13223"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-13223: Type Confusion in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/cve-2025-13224"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-13224: Type Confusion in V8&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the Chromium blog posts:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/11/stable-channel-update-for-desktop_17.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>November 17, 2025&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/11/stable-channel-update-for-desktop_11.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>November 11, 2025&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 3.3.6</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-6/</link><pubDate>Wed, 26 Nov 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-6/</guid><description>&lt;h2 id="chromium-14207444176" data-title>
Chromium 142.0.7444.176&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-14207444176
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces important security fixes. Among them:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/cve-2025-13042"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-13042: Inappropriate implementation in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/cve-2025-13223"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-13223: Type Confusion in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/cve-2025-13224"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-13224: Type Confusion in V8&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the Chromium blog posts:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/11/stable-channel-update-for-desktop_17.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>November 17, 2025&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/11/stable-channel-update-for-desktop_11.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>November 11, 2025&lt;/a>&lt;/li>
&lt;/ul>
&lt;h2 id="quality-enhancements" data-title>
Quality enhancements&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#quality-enhancements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Fixed a &lt;code>NullPointerException&lt;/code> that occurred in WinUI3 when using off-screen rendering mode.&lt;/li>
&lt;li>Fixed an issue where VoiceOver didn’t read elements with &lt;code>aria-live&lt;/code> attributes on macOS.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 2.27.19</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-19/</link><pubDate>Fri, 07 Nov 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-19/</guid><description>&lt;h2 id="chromium-1420744460" data-title>
Chromium 142.0.7444.60&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1420744460
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces important security fixes. Among them:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/cve-2025-11458"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-11458: Heap buffer overflow in Sync&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/cve-2025-11460"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-11460: Use after free in Storage&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the Chromium blog posts:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/10/stable-channel-update-for-desktop_28.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>October 28, 2025&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/10/stable-channel-update-for-desktop_21.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>October 21, 2025&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/10/stable-channel-update-for-desktop_14.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>October 14, 2025&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/10/stable-channel-update-for-desktop_9.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>October 9, 2025&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/10/stable-channel-update-for-desktop.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>October 7, 2025&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 3.3.5</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-5/</link><pubDate>Fri, 07 Nov 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-5/</guid><description>&lt;h2 id="chromium-1420744460" data-title>
Chromium 142.0.7444.60&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1420744460
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces important security fixes. Among them:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/cve-2025-11458"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-11458: Heap buffer overflow in Sync&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/cve-2025-11460"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-11460: Use after free in Storage&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the Chromium blog posts:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/10/stable-channel-update-for-desktop_28.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>October 28, 2025&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/10/stable-channel-update-for-desktop_21.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>October 21, 2025&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/10/stable-channel-update-for-desktop_14.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>October 14, 2025&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/10/stable-channel-update-for-desktop_9.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>October 9, 2025&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/10/stable-channel-update-for-desktop.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>October 7, 2025&lt;/a>&lt;/li>
&lt;/ul>
&lt;h2 id="conversion-from-net-task-to-javascript-promise" data-title>
Conversion from .NET Task to JavaScript Promise&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#conversion-from-net-task-to-javascript-promise
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>DotNetBrowser now supports converting a .NET &lt;code>Task&lt;/code> into a native JavaScript &lt;code>Promise&lt;/code>. This feature was introduced to simplify the process of calling asynchronous .NET methods conveniently from the JavaScript side.&lt;/p></description></item><item><title>DotNetBrowser 2.27.18</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-18/</link><pubDate>Fri, 10 Oct 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-18/</guid><description>&lt;h2 id="chromium-1410739055" data-title>
Chromium 141.0.7390.55&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1410739055
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces important security fixes. Among them:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/cve-2025-11205"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-11205: Heap buffer overflow in WebGPU&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/cve-2025-11206"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-11206: Heap buffer overflow in Video&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the Chromium blog posts:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/09/stable-channel-update-for-desktop_30.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>September 30, 2025&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/09/stable-channel-update-for-desktop_25.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>September 25, 2025&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/09/stable-channel-update-for-desktop_23.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>September 23, 2025&lt;/a>.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 3.3.4</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-4/</link><pubDate>Fri, 10 Oct 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-4/</guid><description>&lt;h2 id="chromium-1410739055" data-title>
Chromium 141.0.7390.55&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1410739055
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces important security fixes. Among them:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/cve-2025-11205"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-11205: Heap buffer overflow in WebGPU&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/cve-2025-11206"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-11206: Heap buffer overflow in Video&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the Chromium blog posts:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/09/stable-channel-update-for-desktop_30.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>September 30, 2025&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/09/stable-channel-update-for-desktop_25.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>September 25, 2025&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2025/09/stable-channel-update-for-desktop_23.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>September 23, 2025&lt;/a>.&lt;/li>
&lt;/ul>
&lt;h2 id="quality-enhancements" data-title>
Quality enhancements&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#quality-enhancements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Fixed the appearance of WinUI3 autofill suggestions in off-screen rendering mode.&lt;/li>
&lt;li>Dialog windows in WinUI3 now function correctly and properly block the parent application window.&lt;/li>
&lt;li>Fixed incorrect diagonal resize cursors in Avalonia when using off-screen rendering mode.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 2.27.17</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-17/</link><pubDate>Wed, 17 Sep 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-17/</guid><description>&lt;h2 id="chromium-14007339133" data-title>
Chromium 140.0.7339.133&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-14007339133
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>DotNetBrowser has been upgraded to Chromium 140.0.7339.133, which includes the latest performance improvements and security patches.
Key security vulnerabilities addressed in this version include:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-10200"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-10200: Use after free in Serviceworker&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-10201"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-10201: Inappropriate implementation in Mojo&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For a comprehensive list of all fixes and improvements in this Chromium version, please refer to the official Chromium &lt;a href="https://chromereleases.googleblog.com/2025/09/stable-channel-update-for-desktop_9.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>blog post&lt;/a>.&lt;/p></description></item><item><title>DotNetBrowser 3.3.3</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-3/</link><pubDate>Wed, 17 Sep 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-3/</guid><description>&lt;h2 id="chromium-14007339133" data-title>
Chromium 140.0.7339.133&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-14007339133
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>DotNetBrowser has been upgraded to Chromium 140.0.7339.133, which includes the latest performance improvements and security patches.
Key security vulnerabilities addressed in this version include:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-10200"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-10200: Use after free in Serviceworker&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-10201"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-10201: Inappropriate implementation in Mojo&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For a comprehensive list of all fixes and improvements in this Chromium version, please refer to the official Chromium &lt;a href="https://chromereleases.googleblog.com/2025/09/stable-channel-update-for-desktop_9.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>blog post&lt;/a>.&lt;/p></description></item><item><title>DotNetBrowser 2.27.16</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-16/</link><pubDate>Thu, 14 Aug 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-16/</guid><description>&lt;h2 id="chromium-1390725867" data-title>
Chromium 139.0.7258.67&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1390725867
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces 12 security fixes. Among them:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-8576"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-8576: Use after free in Extensions&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-8577"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-8577: Inappropriate implementation in Picture In Picture&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-8578"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-8578: Use after free in Cast&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the Chromium &lt;a href="https://chromereleases.googleblog.com/2025/08/stable-channel-update-for-desktop.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>blog post&lt;/a>.&lt;/p>
&lt;h3 id="end-of-support-for-macos-11" data-title>
End of support for macOS 11&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#end-of-support-for-macos-11
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Chromium 139 &lt;a href="https://chromestatus.com/feature/4504090090143744"
class="external-link "
target="_blank"
rel="noopener nofollow"
>no longer supports macOS 11&lt;/a>, so we also dropped support for this version in DotNetBrowser 2.27.16. The latest DotNetBrowser version that supports macOS 11 is &lt;a href="https://teamdev.com/dotnetbrowser/releases/2025/v2-27-15/"
>2.27.15&lt;/a>.&lt;/p></description></item><item><title>DotNetBrowser 3.3.2</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-2/</link><pubDate>Thu, 14 Aug 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-2/</guid><description>&lt;h2 id="chromium-1390725867" data-title>
Chromium 139.0.7258.67&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1390725867
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces 12 security fixes. Among them:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-8576"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-8576: Use after free in Extensions&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-8577"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-8577: Inappropriate implementation in Picture In Picture&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-8578"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-8578: Use after free in Cast&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the Chromium &lt;a href="https://chromereleases.googleblog.com/2025/08/stable-channel-update-for-desktop.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>blog post&lt;/a>.&lt;/p>
&lt;h3 id="end-of-support-for-macos-11" data-title>
End of support for macOS 11&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#end-of-support-for-macos-11
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Chromium 139 &lt;a href="https://chromestatus.com/feature/4504090090143744"
class="external-link "
target="_blank"
rel="noopener nofollow"
>no longer supports macOS 11&lt;/a>, so we also dropped support for this version in DotNetBrowser 3.3.2. The latest DotNetBrowser version that supports macOS 11 is &lt;a href="https://teamdev.com/dotnetbrowser/releases/2025/v3-3-1/"
>3.3.1&lt;/a>.&lt;/p></description></item><item><title>DotNetBrowser 2.27.15</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-15/</link><pubDate>Wed, 16 Jul 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-15/</guid><description>&lt;h2 id="chromium-1380720497" data-title>
Chromium 138.0.7204.97&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1380720497
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces major security fixes including the fix for a
vulnerability that have &lt;strong>known exploits&lt;/strong>:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-6554"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-6554: Type Confusion in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-6555"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-6555: Use after free in Animation&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-6556"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-6556: Insufficient policy enforcement in Loader&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-6557"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-6557: Insufficient data validation in DevTools&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the Chromium blog posts:&lt;/p></description></item><item><title>DotNetBrowser 3.3.1</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-1/</link><pubDate>Wed, 16 Jul 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-1/</guid><description>&lt;h2 id="chromium-1380720497" data-title>
Chromium 138.0.7204.97&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1380720497
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces major security fixes including the fix for a
vulnerability that have &lt;strong>known exploits&lt;/strong>:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-6554"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-6554: Type Confusion in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-6555"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-6555: Use after free in Animation&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-6556"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-6556: Insufficient policy enforcement in Loader&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-6557"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-6557: Insufficient data validation in DevTools&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the Chromium blog posts:&lt;/p></description></item><item><title>DotNetBrowser 2.27.14</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-14/</link><pubDate>Fri, 20 Jun 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-14/</guid><description>&lt;h2 id="chromium-1370715169" data-title>
Chromium 137.0.7151.69&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1370715169
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces major security fixes including the fix for a
vulnerability that have &lt;strong>known exploits&lt;/strong>:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5419"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5419: Out of bounds read and write in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5068"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5068: Use after free in Blink&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5063"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5063: Use after free in Compositing&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5280"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5280: Out of bounds write in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5064"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5064: Inappropriate implementation in Background Fetch API&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5065"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5065: Inappropriate implementation in FileSystemAccess API&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5066"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5066: Inappropriate implementation in Messages&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5281"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5281: Inappropriate implementation in BFCache&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5283"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5283: Use after free in libvpx&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5067"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5067: Inappropriate implementation in Tab Strip&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the Chromium blog posts:&lt;/p></description></item><item><title>DotNetBrowser 3.3.0</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-0/</link><pubDate>Fri, 20 Jun 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v3-3-0/</guid><description>&lt;h2 id="chromium-1370715169" data-title>
Chromium 137.0.7151.69&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1370715169
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces major security fixes including the fix for a
vulnerability that have &lt;strong>known exploits&lt;/strong>:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5419"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5419: Out of bounds read and write in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5068"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5068: Use after free in Blink&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5063"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5063: Use after free in Compositing&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5280"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5280: Out of bounds write in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5064"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5064: Inappropriate implementation in Background Fetch API&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5065"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5065: Inappropriate implementation in FileSystemAccess API&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5066"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5066: Inappropriate implementation in Messages&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5281"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5281: Inappropriate implementation in BFCache&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5283"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5283: Use after free in libvpx&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-5067"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-5067: Inappropriate implementation in Tab Strip&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the Chromium blog posts:&lt;/p></description></item><item><title>DotNetBrowser 2.27.13</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-13/</link><pubDate>Mon, 26 May 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-13/</guid><description>&lt;h2 id="chromium-13607103114" data-title>
Chromium 136.0.7103.114&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-13607103114
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces major security fixes. Among them, a fix for a
vulnerability that have &lt;strong>known exploits&lt;/strong>:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-4664"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-4664: Insufficient policy enforcement in Loader&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>Other fixes are:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-4096"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-4096: Heap buffer overflow in HTML&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-4050"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-4050: Out of bounds memory access in DevTools&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-4051"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-4051: Insufficient data validation in DevTools&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-4052"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-4052: Inappropriate implementation in DevTools&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-4372"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-4372: Use after free in WebAudio&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-4609"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-4609: Incorrect handle provided in unspecified circumstances in Mojo&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the Chromium blog posts:&lt;/p></description></item><item><title>DotNetBrowser 3.2.1</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v3-2-1/</link><pubDate>Mon, 26 May 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v3-2-1/</guid><description>&lt;h2 id="chromium-13607103114" data-title>
Chromium 136.0.7103.114&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-13607103114
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces major security fixes. Among them, a fix for a
vulnerability that have &lt;strong>known exploits&lt;/strong>:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-4664"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-4664: Insufficient policy enforcement in Loader&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>Other fixes are:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-4096"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-4096: Heap buffer overflow in HTML&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-4050"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-4050: Out of bounds memory access in DevTools&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-4051"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-4051: Insufficient data validation in DevTools&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-4052"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-4052: Inappropriate implementation in DevTools&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-4372"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-4372: Use after free in WebAudio&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-4609"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-4609: Incorrect handle provided in unspecified circumstances in Mojo&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the Chromium blog posts:&lt;/p></description></item><item><title>DotNetBrowser 2.27.12</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-12/</link><pubDate>Wed, 23 Apr 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-12/</guid><description>&lt;h2 id="chromium-1350704952" data-title>
Chromium 135.0.7049.52&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1350704952
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces 13 security fixes, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-3068"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-3068: Inappropriate implementation in Intents&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-3069"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-3069: Inappropriate implementation in Extensions&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-3071"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-3071: Inappropriate implementation in Navigations&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the &lt;a href="https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>Chromium&lt;/a> blog post.&lt;/p>
&lt;h2 id="quality-enhancements" data-title>
Quality enhancements&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#quality-enhancements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Fixed the issue when Widevine DRM doesn&amp;rsquo;t work on macOS with the popular streaming services such as Netflix.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 3.2.0</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v3-2-0/</link><pubDate>Wed, 23 Apr 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v3-2-0/</guid><description>&lt;h2 id="chromium-1350704952" data-title>
Chromium 135.0.7049.52&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1350704952
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces 13 security fixes, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-3068"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-3068: Inappropriate implementation in Intents&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-3069"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-3069: Inappropriate implementation in Extensions&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-3071"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-3071: Inappropriate implementation in Navigations&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>You can read more about it in the &lt;a href="https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>Chromium&lt;/a> blog post.&lt;/p>
&lt;h2 id="custom-user-agent-client-hints" data-title>
Custom user agent client hints&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#custom-user-agent-client-hints
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>You can now set custom user agent client hints when creating the IEngine instance - these settings also apply to worker threads.
The following snippet shows how it can be done:&lt;/p></description></item><item><title>DotNetBrowser 2.27.11</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-11/</link><pubDate>Wed, 26 Mar 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-11/</guid><description>&lt;h2 id="chromium-1340699889" data-title>
Chromium 134.0.6998.89&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1340699889
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces 23 security fixes, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-1920"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-1920: Type Confusion in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-24201"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-24201: Out of bounds write in GPU on Mac&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-2137"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-2137: Out of bounds read in V8&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements since the previous Chromium upgrade please visit
the product blog posts for the following versions:&lt;/p></description></item><item><title>DotNetBrowser 3.1.2</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v3-1-2/</link><pubDate>Wed, 26 Mar 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v3-1-2/</guid><description>&lt;h2 id="chromium-1340699889" data-title>
Chromium 134.0.6998.89&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1340699889
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces 23 security fixes, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-1920"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-1920: Type Confusion in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-24201"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-24201: Out of bounds write in GPU on Mac&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-2137"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-2137: Out of bounds read in V8&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements since the previous Chromium upgrade please visit
the product blog posts for the following versions:&lt;/p></description></item><item><title>DotNetBrowser 2.27.10</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-10/</link><pubDate>Mon, 03 Mar 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-10/</guid><description>&lt;h2 id="chromium-1330694399" data-title>
Chromium 133.0.6943.99&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1330694399
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces 21 security fixes, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-0995"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-0995: Use after free in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-0996"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-0996: Inappropriate implementation in Browser UI&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-0997"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-0997: Use after free in Navigation&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements since the previous Chromium upgrade please visit
the product blog posts for the following versions:&lt;/p></description></item><item><title>DotNetBrowser 3.1.1</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v3-1-1/</link><pubDate>Mon, 03 Mar 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v3-1-1/</guid><description>&lt;h2 id="chromium-1330694399" data-title>
Chromium 133.0.6943.99&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1330694399
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces 21 security fixes, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-0995"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-0995: Use after free in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-0996"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-0996: Inappropriate implementation in Browser UI&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-0997"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-0997: Use after free in Navigation&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements since the previous Chromium upgrade please visit
the product blog posts for the following versions:&lt;/p></description></item><item><title>DotNetBrowser 2.27.9</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-9/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-9/</guid><description>&lt;h2 id="quality-enhancements" data-title>
Quality enhancements&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#quality-enhancements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>In the off-screen rendering mode, the autofill suggestions are now accepted properly after selection.&lt;/li>
&lt;li>The WPF &lt;code>BrowserView&lt;/code> now respects the parent container size properly in the off-screen rendering mode.&lt;/li>
&lt;li>In WPF off-screen, the keyboard focus now leaves the &lt;code>BrowserView&lt;/code> after pressing Shift+Tab.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 3.1.0</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v3-1-0/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v3-1-0/</guid><description>&lt;h2 id="customizing-user-agent-client-hints" data-title>
Customizing User-Agent Client Hints&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#customizing-user-agent-client-hints
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>Traditionally, the &lt;code>User-Agent&lt;/code> string has been used to retrieve information about a user&amp;rsquo;s browser or device. However, User-Agent Client Hints offer a more privacy-friendly approach, allowing browsers to limit the amount of information exposed by default. In Chromium, for example, the &lt;code>User-Agent&lt;/code> string now provides only basic details, while more specific data is accessible through the &lt;a href="https://developers.google.com/privacy-sandbox/protections/user-agent#user-agent_client_hints_ua-ch"
class="external-link "
target="_blank"
rel="noopener nofollow"
>User-Agent Client Hints API&lt;/a>.&lt;/p></description></item><item><title>DotNetBrowser 2.27.8</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-8/</link><pubDate>Fri, 24 Jan 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v2-27-8/</guid><description>&lt;h2 id="chromium-1320683484" data-title>
Chromium 132.0.6834.84&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1320683484
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces 16 security fixes, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-0434"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-0434: Out of bounds memory access in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-0435"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-0435: Inappropriate implementation in Navigation&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-0436"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-0436: Integer overflow in Skia&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements since the previous Chromium upgrade please visit
the product blog posts for the following versions:&lt;/p></description></item><item><title>DotNetBrowser 3.0.1</title><link>https://teamdev.com/dotnetbrowser/releases/2025/v3-0-1/</link><pubDate>Fri, 24 Jan 2025 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2025/v3-0-1/</guid><description>&lt;h2 id="chromium-1320683484" data-title>
Chromium 132.0.6834.84&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1320683484
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces 16 security fixes, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-0434"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-0434: Out of bounds memory access in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-0435"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-0435: Inappropriate implementation in Navigation&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-0436"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2025-0436: Integer overflow in Skia&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements since the previous Chromium upgrade please visit
the product blog posts for the following versions:&lt;/p></description></item><item><title>DotNetBrowser 2.27.7</title><link>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-7/</link><pubDate>Thu, 05 Dec 2024 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-7/</guid><description>&lt;h2 id="chromium-1310677870" data-title>
Chromium 131.0.6778.70&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1310677870
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces 12 security fixes, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-11110"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-11110: Inappropriate implementation in Blink&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-11111"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-11111: Inappropriate implementation in Autofill&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-11112"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-11112: Use after free in Media&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-11113"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-11113: Use after free in Accessibility&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-11117"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-11117: Inappropriate implementation in FileSystem&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements since the previous Chromium upgrade please visit
the product blog posts for the following versions:&lt;/p></description></item><item><title>DotNetBrowser 3.0.0</title><link>https://teamdev.com/dotnetbrowser/releases/2024/v3-0-0/</link><pubDate>Tue, 03 Dec 2024 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2024/v3-0-0/</guid><description>&lt;div class="note-block lead">
&lt;p>We are excited to announce the release of DotNetBrowser 3.0.0!&lt;/p>
&lt;/div>
&lt;p>This new major version introduces a number of new features and improvements, including WinUI 3 support, Chrome extensions, custom DOM events, and more. DotNetBrowser now requires .NET Framework 4.6.2 or later.&lt;/p>
&lt;p>We did not change the API significantly, so you can easily migrate your existing code to the new version. However, we recommend that you review &lt;a href="https://teamdev.com/dotnetbrowser/migration/from-v2-to-v3/overview/"
>the migration guide&lt;/a> to learn about the changes and improvements in DotNetBrowser 3.0.0.&lt;/p></description></item><item><title>DotNetBrowser 2.27.6</title><link>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-6/</link><pubDate>Tue, 12 Nov 2024 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-6/</guid><description>&lt;h2 id="chromium-1300672370" data-title>
Chromium 130.0.6723.70&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1300672370
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces multiple security fixes that prevent
a remote attacker from potentially exploiting heap corruption via a crafted HTML page, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-10229"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-10229: Inappropriate implementation in Extensions&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-10230"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-10230: Type Confusion in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-10231"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-10231: Type Confusion in V8&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements since the previous Chromium upgrade please visit
the product blog posts for the following versions:&lt;/p></description></item><item><title>DotNetBrowser 2.27.5</title><link>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-5/</link><pubDate>Wed, 02 Oct 2024 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-5/</guid><description>&lt;h2 id="chromium-1290666859" data-title>
Chromium 129.0.6668.59&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-1290666859
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces multiple security fixes that prevent
a remote attacker from potentially exploiting heap corruption via a crafted HTML page, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-8904"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-8904: Type Confusion in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-8636"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-8636: Heap buffer overflow in Skia&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-8637"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-8637: Use after free in Media Router&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements in DotNetBrowser 2.27.5 please visit
the product blog posts for the following versions:&lt;/p></description></item><item><title>DotNetBrowser 2.27.4</title><link>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-4/</link><pubDate>Fri, 13 Sep 2024 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-4/</guid><description>&lt;h2 id="chromium-upgraded-to-1280661385" data-title>
Chromium upgraded to 128.0.6613.85&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-upgraded-to-1280661385
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces multiple security fixes that prevent a remote attacker from
exploiting heap corruption via a crafted HTML page, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-7971"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-7971: Type Confusion in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-7968"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-7968: Use after free in Autofill&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-7966"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-7966: Out of bounds memory access in Skia&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements in DotNetBrowser 2.27.4 please visit
the product blog posts for the following versions:&lt;/p></description></item><item><title>DotNetBrowser 3.0.0 EAP</title><link>https://teamdev.com/dotnetbrowser/releases/2024/v3-0-0-eap/</link><pubDate>Tue, 20 Aug 2024 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2024/v3-0-0-eap/</guid><description>&lt;div class="note-block lead">
&lt;p>This page contains a complete release history for the DotNetBrowser 3.0.0 EAP builds in reverse chronological order.&lt;/p>
&lt;/div>
&lt;p>To add the latest DotNetBrowser 3.0.0 EAP build dependencies to your project as NuGet packages &lt;a href="https://learn.microsoft.com/en-us/nuget/create-packages/prerelease-packages#installing-and-updating-pre-release-packages"
class="external-link "
target="_blank"
rel="noopener nofollow"
>use the next instruction.&lt;/a>&lt;/p>
&lt;p>To learn more about the enhancements planned for this major release, please visit &lt;a href="https://teamdev.com/dotnetbrowser/roadmap/"
>DotNetBrowser Roadmap&lt;/a>.&lt;/p>
&lt;h2 id="v300-eap2" data-title>
v3.0.0-eap.2&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#v300-eap2
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chrome-extensions" data-title>
Chrome extensions&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chrome-extensions
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>DotNetBrowser now provides the Extensions API that allows you to install, update, uninstall, and work with Chrome extensions. It opens up a wide range of possibilities for integrating Chrome extensions into your applications.&lt;/p></description></item><item><title>DotNetBrowser 2.27.3</title><link>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-3/</link><pubDate>Mon, 05 Aug 2024 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-3/</guid><description>&lt;h2 id="chromium-upgraded-to-1270653373" data-title>
Chromium upgraded to 127.0.6533.73&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-upgraded-to-1270653373
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces multiple security fixes that prevent a remote attacker from
executing arbitrary code via a crafted HTML page, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-6100"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-6100: Type Confusion in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-6290"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-6290: Use after free in Dawn&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-6779"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-6779: Out of bounds memory access in V8&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements in DotNetBrowser 2.27.3 please visit
the product blog posts for the following versions:&lt;/p></description></item><item><title>DotNetBrowser 2.27.2</title><link>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-2/</link><pubDate>Fri, 21 Jun 2024 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-2/</guid><description>&lt;h2 id="chromium-upgraded-to-1260647857" data-title>
Chromium upgraded to 126.0.6478.57&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-upgraded-to-1260647857
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces multiple security fixes that prevent a remote attacker from
potentially exploiting the heap corruption via a crafted HTML page, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-5830"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-5830: Type Confusion in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-5831"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-5831: Use after free in Dawn&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements please visit the product blog posts for the following versions:&lt;/p></description></item><item><title>DotNetBrowser 2.27.1</title><link>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-1/</link><pubDate>Thu, 30 May 2024 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-1/</guid><description>&lt;h2 id="chromium-upgraded-to-12506422113" data-title>
Chromium upgraded to 125.0.6422.113&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-upgraded-to-12506422113
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces multiple security fixes. Among them, a fix for a
vulnerability that &lt;strong>have known exploits&lt;/strong>:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-5274"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-5274: Type Confusion in V8&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements in &lt;code>125.0.6422.113&lt;/code> please visit
the product blog posts for the following versions:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_23.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>125.0.6422.113&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_21.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>125.0.6422.77&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_15.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>125.0.6422.60&lt;/a>&lt;/li>
&lt;/ul>
&lt;h2 id="quality-enhancements" data-title>
Quality enhancements&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#quality-enhancements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>The code signing certificates were updated for DotNetBrowser DLLs and Chromium binaries for Windows.&lt;/li>
&lt;li>The &lt;code>IBrowser.DisposeAsync()&lt;/code> implementation was improved to avoid undefined behavior.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 2.27.0</title><link>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-0/</link><pubDate>Wed, 22 May 2024 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2024/v2-27-0/</guid><description>&lt;h2 id="chromium-upgraded-to-12406367221" data-title>
Chromium upgraded to 124.0.6367.221&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-upgraded-to-12406367221
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces security fixes for vulnerabilities that &lt;strong>have known exploits&lt;/strong>:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-4761"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-4761: Out of bounds write in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-4947"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-4947: Type Confusion in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-4671"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-4671: Use after free in Visuals&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements in &lt;code>124.0.6367.221&lt;/code> please visit the product blog posts for the following versions:&lt;/p></description></item><item><title>DotNetBrowser 2.26.2</title><link>https://teamdev.com/dotnetbrowser/releases/2024/v2-26-2/</link><pubDate>Wed, 24 Apr 2024 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2024/v2-26-2/</guid><description>&lt;h2 id="chromium-upgraded-to-12306312124" data-title>
Chromium upgraded to 123.0.6312.124&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-upgraded-to-12306312124
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces multiple security fixes that prevent a remote attacker who had compromised the GPU process from potentially perform a sandbox escape via specific UI gestures, potentially exploit heap corruption via a crafted HTML page, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-3157"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-3157: Out of bounds write in Compositing&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-3516"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-3516: Heap buffer overflow in ANGLE&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-3515"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-3515: Use after free in Dawn&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-3159"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-3159: Out of bounds memory access in V8&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements in &lt;code>123.0.6312.124&lt;/code> please visit
the product blog posts for the following versions:&lt;/p></description></item><item><title>DotNetBrowser 2.26.1</title><link>https://teamdev.com/dotnetbrowser/releases/2024/v2-26-1/</link><pubDate>Thu, 28 Mar 2024 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2024/v2-26-1/</guid><description>&lt;h2 id="chromium-upgraded-to-1220626194" data-title>
Chromium upgraded to 122.0.6261.94&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-upgraded-to-1220626194
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces multiple security fixes that prevent a remote attacker from
potentially exploiting the heap corruption via a crafted HTML page, including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-1669"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-1669: Out of bounds memory access in Blink&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-1670"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-1670: Use after free in Mojo&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-1938"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-1938: Type Confusion in V8&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2024-1939"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2024-1939: Type Confusion in V8&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements in &lt;code>122.0.6261.94&lt;/code> please visit
the product blog posts for the following versions:&lt;/p></description></item><item><title>DotNetBrowser 2.26.0</title><link>https://teamdev.com/dotnetbrowser/releases/2024/v2-26-0/</link><pubDate>Tue, 27 Feb 2024 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2024/v2-26-0/</guid><description>&lt;h2 id="casting-api" data-title>
Casting API&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#casting-api
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>It’s now possible to cast media content directly from DotNetBrowser to the devices supported by Chromium. Here’s how easy it is:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-csharp" data-lang="csharp">&lt;span class="line">&lt;span class="cl">&lt;span class="n">IMediaReceivers&lt;/span> &lt;span class="n">receivers&lt;/span> &lt;span class="p">=&lt;/span> &lt;span class="n">engine&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Profile&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Default&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">MediaCasting&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Receivers&lt;/span>&lt;span class="p">;&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="n">IMediaReceiver&lt;/span> &lt;span class="n">receiver&lt;/span> &lt;span class="p">=&lt;/span> &lt;span class="k">await&lt;/span> &lt;span class="n">receivers&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">RetrieveAsync&lt;/span>&lt;span class="p">(&lt;/span>&lt;span class="n">r&lt;/span> &lt;span class="p">=&amp;gt;&lt;/span> &lt;span class="n">r&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Supports&lt;/span>&lt;span class="p">(&lt;/span>&lt;span class="n">CastMode&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Screen&lt;/span>&lt;span class="p">));&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="n">ICastSession&lt;/span> &lt;span class="n">castSession&lt;/span> &lt;span class="p">=&lt;/span> &lt;span class="k">await&lt;/span> &lt;span class="n">browser&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Cast&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">CastScreen&lt;/span>&lt;span class="p">(&lt;/span>&lt;span class="n">receiver&lt;/span>&lt;span class="p">);&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Check out the complete &lt;a href="https://teamdev.com/dotnetbrowser/docs/guides/gs/media/#casting"
>guide&lt;/a> to learn more about this functionality.&lt;/p>
&lt;h2 id="chromium-upgraded-to-12106167184" data-title>
Chromium upgraded to 121.0.6167.184&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-upgraded-to-12106167184
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces multiple security fixes that prevent a remote attacker to
potentially exploit heap corruption via a crafted HTML page or malicious file, including:&lt;/p></description></item><item><title>DotNetBrowser 2.25.1</title><link>https://teamdev.com/dotnetbrowser/releases/2024/v2-25-1/</link><pubDate>Mon, 22 Jan 2024 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2024/v2-25-1/</guid><description>&lt;h2 id="savefilehandler-dialog-handler" data-title>
&lt;code>SaveFileHandler&lt;/code> dialog handler&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#savefilehandler-dialog-handler
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>In this version, we introduce a new handler that is invoked when the browser executes &lt;a href="https://developer.mozilla.org/en-US/docs/Web/API/Window/showSaveFilePicker"
class="external-link "
target="_blank"
rel="noopener nofollow"
>&lt;code>window.showSaveFilePicker()&lt;/code>&lt;/a> on the web page.&lt;/p>
&lt;p>If there&amp;rsquo;s a &lt;code>BrowserView&lt;/code> initialized from this browser, it will show the default file picker. You can also handle this directly in your code and provide a file programmatically:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-csharp" data-lang="csharp">&lt;span class="line">&lt;span class="cl">&lt;span class="n">Browser&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Dialogs&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">SaveFileHandler&lt;/span> &lt;span class="p">=&lt;/span> &lt;span class="k">new&lt;/span> &lt;span class="n">Handler&lt;/span>&lt;span class="p">&amp;lt;&lt;/span>&lt;span class="n">SaveFileParameters&lt;/span>&lt;span class="p">,&lt;/span> &lt;span class="n">SaveFileResponse&lt;/span>&lt;span class="p">&amp;gt;(&lt;/span>&lt;span class="n">p&lt;/span> &lt;span class="p">=&amp;gt;&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="p">{&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="k">return&lt;/span> &lt;span class="n">SaveFileResponse&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">SaveToFile&lt;/span>&lt;span class="p">(&lt;/span>&lt;span class="n">fileName&lt;/span>&lt;span class="p">);&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="p">});&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="chromium-upgraded-to-12006099216" data-title>
Chromium upgraded to 120.0.6099.216&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-upgraded-to-12006099216
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We upgraded Chromium to a newer version, which introduces multiple security fixes, including:&lt;/p></description></item><item><title>DotNetBrowser 2.25.0</title><link>https://teamdev.com/dotnetbrowser/releases/2023/v2-25-0/</link><pubDate>Wed, 27 Dec 2023 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2023/v2-25-0/</guid><description>&lt;h2 id="blazor-hybrid-template-for-avalonia-ui" data-title>
Blazor Hybrid template for Avalonia UI&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#blazor-hybrid-template-for-avalonia-ui
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>The &lt;a href="https://www.nuget.org/packages/DotNetBrowser.Templates"
class="external-link "
target="_blank"
rel="noopener nofollow"
>DotNetBrowser.Templates&lt;/a> package now contains one more template - a simple Blazor Hybrid application that utilizes the capabilities of Avalonia UI and DotNetBrowser to run Razor components in a desktop app. This approach can be used to build a cross-platform desktop application and construct its UI using both Blazor and Avalonia UI capabilities, sharing a large amount of code between web and desktop. See our &lt;a href="https://teamdev.com/dotnetbrowser/docs/quickstart/avalonia-blazor/"
>Quick Start guide&lt;/a> for more details.&lt;/p></description></item><item><title>DotNetBrowser 2.24.2</title><link>https://teamdev.com/dotnetbrowser/releases/2023/v2-24-2/</link><pubDate>Wed, 22 Nov 2023 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2023/v2-24-2/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium" data-title>
Chromium&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We upgraded Chromium to a newer version, which introduces &lt;a href="https://chromereleases.googleblog.com/2023/10/stable-channel-update-for-desktop_31.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>several security fixes&lt;/a> including:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2023-5480"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2023-5480: Inappropriate implementation in Payments&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2023-5482"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2023-5482: Insufficient data validation in USB&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2023-5849"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2023-5849: Integer overflow in USB&lt;/a>.&lt;/li>
&lt;/ul>
&lt;p>For the complete list of Chromium fixes and improvements in 119.0.6045.105 please visit the product &lt;a href="https://chromereleases.googleblog.com/2023/10/stable-channel-update-for-desktop_31.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>blog post for this version&lt;/a>.&lt;/p></description></item><item><title>DotNetBrowser 2.24.1</title><link>https://teamdev.com/dotnetbrowser/releases/2023/v2-24-1/</link><pubDate>Fri, 20 Oct 2023 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2023/v2-24-1/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium" data-title>
Chromium&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We upgraded Chromium to 118.0.5993.70.&lt;/p>
&lt;p>You can see the complete list of changes &lt;a href="https://chromereleases.googleblog.com/2023/10/stable-channel-update-for-desktop_10.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>here&lt;/a>.
In particular, this version contains the fix for &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2023-5218"
class="external-link "
target="_blank"
rel="noopener nofollow"
>CVE-2023-5218: Use after free in Site Isolation&lt;/a>.&lt;/p>
&lt;h2 id="quality-enhancements" data-title>
Quality enhancements&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#quality-enhancements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Improved the &lt;code>IsSession&lt;/code> property behavior in &lt;code>CanSetCookieHandler&lt;/code>.&lt;/li>
&lt;li>Fixed an issue with the unselectable combo box in WPF touchscreen applications in the offscreen rendering mode.&lt;/li>
&lt;li>Fixed an issue with an exception handling in the default context menu.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 2.24</title><link>https://teamdev.com/dotnetbrowser/releases/2023/v2-24/</link><pubDate>Tue, 03 Oct 2023 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2023/v2-24/</guid><description>&lt;div class="note-block lead">
&lt;p>A long awaited Avalonia UI support and a new Chromium with security updates.&lt;/p>
&lt;/div>
&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="avalonia-ui" data-title>
Avalonia UI&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#avalonia-ui
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We&amp;rsquo;re delighted to announce DotNetBrowser&amp;rsquo;s support for Avalonia UI!&lt;/p>
&lt;p>With yet another integration in the toolbox, DotNetBrowser has become the most versatile web view control for .NET
on Windows, Linux, and macOS.&lt;/p>
&lt;p>Check out &lt;a href="https://teamdev.com/dotnetbrowser/docs/quickstart/avalonia/"
>the quick start guide&lt;/a> and build a cross-platform
application in just 5 minutes.&lt;/p></description></item><item><title>DotNetBrowser 2.23.3</title><link>https://teamdev.com/dotnetbrowser/releases/2023/v2-23-3/</link><pubDate>Wed, 06 Sep 2023 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2023/v2-23-3/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium" data-title>
Chromium&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We&amp;rsquo;ve upgraded Chromium to version 116.0.5845.140.
The full list of changes since the last upgrade:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2023/08/stable-channel-update-for-desktop_15.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>Chromium 116.0.5845.96&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2023/08/chrome-desktop-stable-update.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>Chromium 116.0.5845.110&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://chromereleases.googleblog.com/2023/08/stable-channel-update-for-desktop_29.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>Chromium 116.0.5845.140&lt;/a>&lt;/li>
&lt;/ul>
&lt;h2 id="quality-enhancements" data-title>
Quality enhancements&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#quality-enhancements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Added support for the H265/HEVC codec.&lt;/li>
&lt;li>Improved the behavior of the BrowserView toolbox component in WinForms applications (DotNetBrowser VSIX package).&lt;/li>
&lt;li>Enabled overriding of the &lt;code>AmbientAuthenticationInPrivateModesEnabled&lt;/code> policy.&lt;/li>
&lt;li>Improved initial locations of dialog windows.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 2.23.2</title><link>https://teamdev.com/dotnetbrowser/releases/2023/v2-23-2/</link><pubDate>Thu, 03 Aug 2023 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2023/v2-23-2/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium" data-title>
Chromium&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We&amp;rsquo;ve upgraded Chromium to version 115.0.5790.99. This update includes &lt;a href="https://chromereleases.googleblog.com/2023/07/stable-channel-update-for-desktop.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>20 security fixes&lt;/a>.&lt;/p>
&lt;h2 id="quality-enhancements" data-title>
Quality enhancements&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#quality-enhancements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Fixed an issue with printing via system printer.&lt;/li>
&lt;li>Fixed an issue when AJAX requests did not work with custom URI scheme.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 2.23.1</title><link>https://teamdev.com/dotnetbrowser/releases/2023/v2-23-1/</link><pubDate>Thu, 22 Jun 2023 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2023/v2-23-1/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium" data-title>
Chromium&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We upgraded Chromium to version 114.0.5735.134 which includes &lt;a href="https://chromereleases.googleblog.com/2023/06/stable-channel-update-for-desktop_13.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>5 security fixes&lt;/a>.&lt;/p>
&lt;h2 id="quality-enhancements" data-title>
Quality enhancements&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#quality-enhancements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Fixed application freeze caused by the default &lt;code>BeforeUnloadHandler&lt;/code>.&lt;/li>
&lt;li>Fixed application freeze caused by &amp;ldquo;Save credit card&amp;rdquo; dialog.&lt;/li>
&lt;li>Fixed DRM content playback issue.&lt;/li>
&lt;li>Fixed the inability to put focus on the input field after confirming modal dialog.&lt;/li>
&lt;li>Improved parent window detection if there is no parent WPF or WinForms window.&lt;/li>
&lt;li>DevTools window title now displays the URL of the opened page.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 2.23</title><link>https://teamdev.com/dotnetbrowser/releases/2023/v2-23/</link><pubDate>Thu, 25 May 2023 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2023/v2-23/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="touchscreen-support" data-title>
Touchscreen support&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#touchscreen-support
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Starting with this update, DotNetBrowser works on touchscreen devices in the off-screen rendering mode. That includes scroll, long-press, pinch-to-zoom, and content rotation.&lt;/p>
&lt;div class="note-block note">
&lt;p>Full touch and gestures support is available in WPF. In WinForms, this functionality is limited to tapping and long-pressing, because touch support in WinForms itself is limited.&lt;/p>
&lt;/div>
&lt;h3 id="chromium" data-title>
Chromium&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We upgraded Chromium to version 113.0.5672.63 which includes &lt;a href="https://chromereleases.googleblog.com/2023/05/stable-channel-update-for-desktop.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>15 security fixes&lt;/a>.&lt;/p></description></item><item><title>DotNetBrowser 2.22.1</title><link>https://teamdev.com/dotnetbrowser/releases/2023/v2-22-1/</link><pubDate>Thu, 27 Apr 2023 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2023/v2-22-1/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium-112" data-title>
Chromium 112&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-112
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>In this release, we upgraded Chromium engine to version 112.0.5615.137 that includes &lt;a href="https://chromereleases.googleblog.com/2023/04/stable-channel-update-for-desktop_18.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>8 security fixes.&lt;/a>&lt;/p>
&lt;h3 id="default-font-size" data-title>
Default font size&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#default-font-size
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Modify the default font size of the webpage loaded in &lt;code>IBrowser&lt;/code> instance with the help of a new setting:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-csharp" data-lang="csharp">&lt;span class="line">&lt;span class="cl">&lt;span class="n">browser&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Settings&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">DefaultFontSize&lt;/span> &lt;span class="p">=&lt;/span> &lt;span class="m">22&lt;/span>&lt;span class="p">;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="quality-enhancements" data-title>
Quality enhancements&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#quality-enhancements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Fixed issue when HTML5 color picker did not function properly.&lt;/li>
&lt;li>Switched pixel format to Pbgra32 that slightly improves off-screen rendering performance in WPF.&lt;/li>
&lt;li>The path to a log file is now automatically created if it does not exist.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 2.22</title><link>https://teamdev.com/dotnetbrowser/releases/2023/v2-22/</link><pubDate>Thu, 23 Mar 2023 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2023/v2-22/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium" data-title>
Chromium&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We upgraded the Chromium engine to version 111.0.5563.65 which includes &lt;a href="https://chromereleases.googleblog.com/2023/03/stable-channel-update-for-desktop.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>40 security fixes.&lt;/a>&lt;/p>
&lt;h3 id="asynchronous-javascript-execution" data-title>
Asynchronous JavaScript execution&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#asynchronous-javascript-execution
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We added &lt;code>InvokeAsync()&lt;/code> methods to &lt;code>IJsObject&lt;/code> and &lt;code>IJsFunction&lt;/code>. It allows executing JavaScript functions without blocking the current .NET thread:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-csharp" data-lang="csharp">&lt;span class="line">&lt;span class="cl">&lt;span class="n">IJsObject&lt;/span> &lt;span class="n">window&lt;/span> &lt;span class="p">=&lt;/span> &lt;span class="n">frame&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">ExecuteJavaScript&lt;/span>&lt;span class="p">&amp;lt;&lt;/span>&lt;span class="n">IJsObject&lt;/span>&lt;span class="p">&amp;gt;(&lt;/span>&lt;span class="s">&amp;#34;window&amp;#34;&lt;/span>&lt;span class="p">).&lt;/span>&lt;span class="n">Result&lt;/span>&lt;span class="p">;&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="n">window&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">InvokeAsync&lt;/span>&lt;span class="p">(&lt;/span>&lt;span class="s">&amp;#34;alert&amp;#34;&lt;/span>&lt;span class="p">,&lt;/span> &lt;span class="s">&amp;#34;Hello world!&amp;#34;&lt;/span>&lt;span class="p">);&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h3 id="network-prediction" data-title>
Network prediction&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#network-prediction
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Chromium has a default setting that allows preloading the most visited pages for faster browsing. This is done by DNS prefetching, TCP and SSL preconnection, prerendering of web pages, and resource prefetching.&lt;/p></description></item><item><title>DotNetBrowser 2.21</title><link>https://teamdev.com/dotnetbrowser/releases/2023/v2-21/</link><pubDate>Mon, 27 Feb 2023 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2023/v2-21/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="windows-arm" data-title>
Windows ARM&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#windows-arm
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>From now on, you can use DotNetBrowser on Windows devices with ARM64 architecture. See what packages to install from &lt;a href="https://teamdev.com/dotnetbrowser/docs/guides/installation/nuget/#windows-arm64"
>NuGet&lt;/a> or &lt;a href="https://teamdev.com/dotnetbrowser/docs/guides/installation/zip/#windows-arm64"
>ZIP&lt;/a>.&lt;/p>
&lt;h3 id="chromium" data-title>
Chromium&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We upgraded Chromium to version 110.0.5481.77. This update includes &lt;a href="https://chromereleases.googleblog.com/2023/02/stable-channel-update-for-desktop.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>15 security fixes&lt;/a>.&lt;/p>
&lt;div class="note-block note">
&lt;p>Starting with this version, Chromium requires minimum Windows 10 or Windows Server 2016. The same requirements are for DotNetBrowser.&lt;/p></description></item><item><title>DotNetBrowser 2.20.1</title><link>https://teamdev.com/dotnetbrowser/releases/2023/v2-20-1/</link><pubDate>Tue, 07 Feb 2023 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2023/v2-20-1/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium" data-title>
Chromium&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We&amp;rsquo;ve bumped Chromium to version 108.0.5359.215.&lt;/p>
&lt;h3 id="clearing-http-authentication-cache" data-title>
Clearing HTTP authentication cache&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#clearing-http-authentication-cache
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>The API has been extended with functionality that allows you to clear HTTP authentication cache:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-csharp" data-lang="csharp">&lt;span class="line">&lt;span class="cl">&lt;span class="n">profile&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">HttpAuthCache&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Clear&lt;/span>&lt;span class="p">();&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h3 id="forwarding-mouse-modifiers" data-title>
Forwarding mouse modifiers&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#forwarding-mouse-modifiers
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>With these changes, it is possible to forward mouse modifiers along with the mouse input events to indicate which mouse buttons are in the pressed state during these events. For instance, we can simulate the mouse moved event with the left mouse button pressed:&lt;/p></description></item><item><title>DotNetBrowser 2.20</title><link>https://teamdev.com/dotnetbrowser/releases/2022/v2-20/</link><pubDate>Wed, 28 Dec 2022 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2022/v2-20/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium-108" data-title>
Chromium 108&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-108
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We upgraded Chromium to version 108.0.5359.125 which includes 8 &lt;a href="https://chromereleases.googleblog.com/2022/12/stable-channel-update-for-desktop_13.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>important security fixes&lt;/a>.&lt;/p>
&lt;h3 id="late-binding-support-for-vbnet" data-title>
Late binding support for VB.NET&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#late-binding-support-for-vbnet
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We&amp;rsquo;ve improved the existing &lt;code>dynamic&lt;/code> support to make it work better for VB.NET. It is now possible to get JavaScript object properties with &lt;a href="https://learn.microsoft.com/en-us/dotnet/visual-basic/programming-guide/language-features/early-late-binding/"
class="external-link "
target="_blank"
rel="noopener nofollow"
>late binding&lt;/a>. For example:&lt;/p></description></item><item><title>DotNetBrowser 2.19</title><link>https://teamdev.com/dotnetbrowser/releases/2022/v2-19/</link><pubDate>Mon, 05 Dec 2022 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2022/v2-19/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="arm" data-title>
ARM&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#arm
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Use DotNetBrowser on Linux and macOS with ARM64 architecture.&lt;/p>
&lt;p>The library has been tested with the following hardware and software:&lt;/p>
&lt;ul>
&lt;li>Raspberry Pi 2 (A 900MHz quad-core ARM Cortex-A7 CPU) and AWS (AWS Graviton Processors) with Ubuntu 20.04 LTS&lt;/li>
&lt;li>Apple Silicon M1 with macOS Big Sur&lt;/li>
&lt;/ul>
&lt;p>The library includes Chromium binaries compiled for ARM architecture. See what packages to install in your project for &lt;a href="https://teamdev.com/dotnetbrowser/docs/guides/installation/nuget/#linux-arm64"
>Linux&lt;/a> and &lt;a href="https://teamdev.com/dotnetbrowser/docs/guides/installation/nuget/#macos-arm64"
>macOS&lt;/a>.&lt;/p></description></item><item><title>DotNetBrowser 2.18</title><link>https://teamdev.com/dotnetbrowser/releases/2022/v2-18/</link><pubDate>Fri, 21 Oct 2022 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2022/v2-18/</guid><description>&lt;div class="note-block lead">
&lt;p>This release comes with Chromium 106 and navigation improvement.&lt;/p>
&lt;/div>
&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium" data-title>
Chromium&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We&amp;rsquo;ve upgraded Chromium to version 106.0.5249.119. It includes fixes from &lt;a href="https://chromereleases.googleblog.com/2022/09/stable-channel-update-for-desktop_14.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>Chromium 105&lt;/a>, &lt;a href="https://chromereleases.googleblog.com/2022/09/stable-channel-update-for-desktop_27.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>Chromium 106&lt;/a>, and the latest &lt;a href="https://chromereleases.googleblog.com/2022/09/stable-channel-update-for-desktop_30.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>Stable channel&lt;/a> update.&lt;/p>
&lt;h3 id="navigation" data-title>
Navigation&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#navigation
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>The &lt;code>LoadResult&lt;/code> was replaced with &lt;code>NavigationResult&lt;/code> to provide more details about the possible navigation failure. Before this change, the &lt;code>LoadUrl()&lt;/code> method returned &lt;code>Task&amp;lt;LoadResult&amp;gt;&lt;/code> that could only be used to determine whether the navigation has succeeded or failed.&lt;/p></description></item><item><title>DotNetBrowser 2.17</title><link>https://teamdev.com/dotnetbrowser/releases/2022/v2-17/</link><pubDate>Wed, 05 Oct 2022 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2022/v2-17/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser&amp;rsquo;s history is getting a new spin! We are happy to announce that DotNetBrowser is a cross-platform library now!&lt;/p>
&lt;/div>
&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="available-on-linux-and-macos" data-title>
Available on Linux and macOS&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#available-on-linux-and-macos
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Starting with version 2.17, the library also works on Linux and macOS.&lt;/p>
&lt;video width="481" height="120" class="demo" data-border-radius="11px" data-caption="">
&lt;source src="https://teamdev.com/dotnetbrowser/videos/releases/2-17/macos-example.mp4" type="video/mp4">
&lt;video-caption>DotNetBrowser &lt;a href="https://teamdev.com/dotnetbrowser/docs/quickstart/console/">application&lt;/a> on macOS&lt;/video-caption>
&lt;/video>
&lt;video width="492" height="142" class="demo" data-border-radius="5px" data-caption="DotNetBrowser on Linux">
&lt;source src="https://teamdev.com/dotnetbrowser/videos/releases/2-17/linux-example.mp4" type="video/mp4">
&lt;video-caption>DotNetBrowser &lt;a href="https://teamdev.com/dotnetbrowser/docs/quickstart/console/">application&lt;/a> on Ubuntu&lt;/video-caption>
&lt;/video>
&lt;p>Use the same code on all three platforms with no extra effort. Simply install the new binaries:&lt;/p></description></item><item><title>DotNetBrowser 2.16.1</title><link>https://teamdev.com/dotnetbrowser/releases/2022/v2-16-1/</link><pubDate>Tue, 23 Aug 2022 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2022/v2-16-1/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We&amp;rsquo;ve added the possibility to create IEngine asynchronously:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-csharp" data-lang="csharp">&lt;span class="line">&lt;span class="cl">&lt;span class="kd">public&lt;/span> &lt;span class="n">Form1&lt;/span>&lt;span class="p">()&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="p">{&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">InitializeComponent&lt;/span>&lt;span class="p">();&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">EngineFactory&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">CreateAsync&lt;/span>&lt;span class="p">(&lt;/span>&lt;span class="k">new&lt;/span> &lt;span class="n">EngineOptions&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Builder&lt;/span>&lt;span class="p">()&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="p">{&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">RenderingMode&lt;/span> &lt;span class="p">=&lt;/span> &lt;span class="n">RenderingMode&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">HardwareAccelerated&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="p">}.&lt;/span>&lt;span class="n">Build&lt;/span>&lt;span class="p">()).&lt;/span>&lt;span class="n">ContinueWith&lt;/span>&lt;span class="p">(&lt;/span>&lt;span class="n">t&lt;/span> &lt;span class="p">=&amp;gt;&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="p">{&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">engine&lt;/span> &lt;span class="p">=&lt;/span> &lt;span class="n">t&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Result&lt;/span>&lt;span class="p">;&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">browser&lt;/span> &lt;span class="p">=&lt;/span> &lt;span class="n">engine&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">CreateBrowser&lt;/span>&lt;span class="p">();&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">browserView&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">InitializeFrom&lt;/span>&lt;span class="p">(&lt;/span>&lt;span class="n">browser&lt;/span>&lt;span class="p">);&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">browser&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Navigation&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">LoadUrl&lt;/span>&lt;span class="p">(&lt;/span>&lt;span class="s">&amp;#34;google.com&amp;#34;&lt;/span>&lt;span class="p">);&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="p">},&lt;/span> &lt;span class="n">TaskScheduler&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">FromCurrentSynchronizationContext&lt;/span>&lt;span class="p">());&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="p">}&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="quality-enhancement" data-title>
Quality enhancement&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#quality-enhancement
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Fixed the issue when IME caused unexpected application termination in Off-screen rendering mode.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 2.16</title><link>https://teamdev.com/dotnetbrowser/releases/2022/v2-16/</link><pubDate>Mon, 08 Aug 2022 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2022/v2-16/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="dynamic-type-support-for-ijsobject" data-title>
Dynamic type support for IJsObject&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#dynamic-type-support-for-ijsobject
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We continue improving the ease-of-use of our product. Now the following syntax is possible:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-csharp" data-lang="csharp">&lt;span class="line">&lt;span class="cl">&lt;span class="kt">dynamic&lt;/span> &lt;span class="n">document&lt;/span> &lt;span class="p">=&lt;/span> &lt;span class="n">Browser&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">MainFrame&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">ExecuteJavaScript&lt;/span>&lt;span class="p">(&lt;/span>&lt;span class="s">&amp;#34;document&amp;#34;&lt;/span>&lt;span class="p">).&lt;/span>&lt;span class="n">Result&lt;/span>&lt;span class="p">;&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="n">document&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">write&lt;/span>&lt;span class="p">(&lt;/span>&lt;span class="s">&amp;#34;Hello world!&amp;#34;&lt;/span>&lt;span class="p">);&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h3 id="chromium" data-title>
Chromium&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Chromium has been upgraded to version 102.0.5005.167. It includes the &lt;a href="https://chromereleases.googleblog.com/2022/07/extended-stable-channel-update-for.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>critical security fix&lt;/a>.&lt;/p>
&lt;h3 id="webauthn-support" data-title>
WebAuthn support&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#webauthn-support
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>It is now possible to authenticate using hardware tokens or built-in platform authenticators such as fingerprint sensors.&lt;/p></description></item><item><title>DotNetBrowser 2.15.1</title><link>https://teamdev.com/dotnetbrowser/releases/2022/v2-15-1/</link><pubDate>Fri, 17 Jun 2022 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2022/v2-15-1/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium" data-title>
Chromium&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Chromium has been upgraded to version 102.0.5005.115 including &lt;a href="https://chromereleases.googleblog.com/2022/06/stable-channel-update-for-desktop.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>7 security fixes&lt;/a>.&lt;/p>
&lt;h3 id="ssl-certificate-verification" data-title>
SSL certificate verification&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#ssl-certificate-verification
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We added user-friendly descriptions of the certificate verification errors to &lt;code>VerifyCertificateHandler&lt;/code>.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-csharp" data-lang="csharp">&lt;span class="line">&lt;span class="cl">&lt;span class="n">Engine&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Profiles&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Default&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Network&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">VerifyCertificateHandler&lt;/span> &lt;span class="p">=&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="k">new&lt;/span> &lt;span class="n">Handler&lt;/span>&lt;span class="p">&amp;lt;&lt;/span>&lt;span class="n">VerifyCertificateParameters&lt;/span>&lt;span class="p">,&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">VerifyCertificateResponse&lt;/span>&lt;span class="p">&amp;gt;(&lt;/span>&lt;span class="n">p&lt;/span> &lt;span class="p">=&amp;gt;&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="p">{&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="k">foreach&lt;/span> &lt;span class="p">(&lt;/span>&lt;span class="n">CertificateVerificationError&lt;/span> &lt;span class="n">verificationError&lt;/span> &lt;span class="k">in&lt;/span> &lt;span class="n">p&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">VerifyErrors&lt;/span>&lt;span class="p">)&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="p">{&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">Console&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">WriteLine&lt;/span>&lt;span class="p">(&lt;/span>&lt;span class="s">&amp;#34;CertificateVerificationStatus = &amp;#34;&lt;/span> &lt;span class="p">+&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">verificationError&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">VerifyStatus&lt;/span>&lt;span class="p">);&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">Console&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">WriteLine&lt;/span>&lt;span class="p">(&lt;/span>&lt;span class="s">&amp;#34;Short description = &amp;#34;&lt;/span> &lt;span class="p">+&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">verificationError&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">ShortDescription&lt;/span>&lt;span class="p">);&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">Console&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">WriteLine&lt;/span>&lt;span class="p">(&lt;/span>&lt;span class="s">&amp;#34;Detailed description = &amp;#34;&lt;/span> &lt;span class="p">+&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">verificationError&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">DetailedDescription&lt;/span>&lt;span class="p">);&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="p">}&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="k">return&lt;/span> &lt;span class="n">VerifyCertificateResponse&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Valid&lt;/span>&lt;span class="p">();&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="p">});&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div></description></item><item><title>DotNetBrowser 2.15</title><link>https://teamdev.com/dotnetbrowser/releases/2022/v2-15/</link><pubDate>Tue, 14 Jun 2022 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2022/v2-15/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium" data-title>
Chromium&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>The Chromium engine has been upgraded to version 102.0.5005.63. It includes &lt;a href="https://chromereleases.googleblog.com/2022/05/stable-channel-update-for-desktop_24.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>32 security fixes&lt;/a>.&lt;/p>
&lt;h3 id="loading-pdf" data-title>
Loading PDF&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#loading-pdf
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We&amp;rsquo;ve improved &lt;a href="https://teamdev.com/dotnetbrowser/docs/guides/gs/navigation/#frame-load-finished"
>FrameLoadFinished&lt;/a> event. It is now fired when the PDF document is loaded completely.&lt;/p>
&lt;h3 id="client-certificate-chain" data-title>
Client certificate chain&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#client-certificate-chain
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Now the library sends the whole chain (end-entity and intermediate certificates) to the server from PKCS#12 store during &lt;a href="https://teamdev.com/dotnetbrowser/docs/guides/gs/authentication/#https-client-certificate"
>client certificate authentication&lt;/a>.&lt;/p></description></item><item><title>DotNetBrowser 2.14</title><link>https://teamdev.com/dotnetbrowser/releases/2022/v2-14/</link><pubDate>Fri, 29 Apr 2022 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2022/v2-14/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium" data-title>
Chromium&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Chromium has been upgraded to version 100.0.4896.127.&lt;/p>
&lt;p>This Chromium version &lt;a href="https://chromereleases.googleblog.com/2022/04/stable-channel-update-for-desktop_14.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>includes&lt;/a> 2 important security fixes.&lt;/p>
&lt;h3 id="caret-browsing" data-title>
Caret browsing&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#caret-browsing
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Now you can use the text cursor to navigate web pages, select text, and click links with your keyboard instead of your mouse:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-csharp" data-lang="csharp">&lt;span class="line">&lt;span class="cl">&lt;span class="n">Browser&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Profile&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Preferences&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">CaretBrowsingEnabled&lt;/span> &lt;span class="p">=&lt;/span> &lt;span class="kc">true&lt;/span>&lt;span class="p">;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h3 id="webform-autofill" data-title>
Webform autofill&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#webform-autofill
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;h4 id="user-data-profile" data-title>
User data profile&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#user-data-profile
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h4>
&lt;p>Autofill web forms with user data profile that includes address, city, phone, first name, etc.&lt;/p></description></item><item><title>DotNetBrowser 2.13.1</title><link>https://teamdev.com/dotnetbrowser/releases/2022/v2-13-1/</link><pubDate>Tue, 12 Apr 2022 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2022/v2-13-1/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium-100" data-title>
Chromium 100&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-100
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Chromium has been upgraded to version 100.0.4896.75. This version &lt;a href="https://chromereleases.googleblog.com/2022/04/stable-channel-update-for-desktop.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>includes&lt;/a> 1 important security fix.&lt;/p>
&lt;h3 id="print-preview-events" data-title>
Print preview events&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#print-preview-events
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Use &lt;code>PrintPreviewOpened&lt;/code> and &lt;code>PrintPreviewClosed&lt;/code> events to get notifications when the Print Preview dialog has been opened or closed.&lt;/p></description></item><item><title>DotNetBrowser 2.13</title><link>https://teamdev.com/dotnetbrowser/releases/2022/v2-13/</link><pubDate>Thu, 07 Apr 2022 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2022/v2-13/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="password-manager-api" data-title>
Password Manager API&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#password-manager-api
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Chromium has built-in functionality that is used to store the entered credentials after the user submits a web form with a username and password. In this case, the &lt;code>SavePasswordHandler&lt;/code> and &lt;code>UpdatePasswordHandler&lt;/code> handlers will be used to decide whether to save credentials or update them if they are already saved.&lt;/p>
&lt;p>To save or update user credentials programmatically, use &lt;code>SavePasswordHandler&lt;/code> and &lt;code>UpdatePasswordHandler&lt;/code> as shown below:&lt;/p></description></item><item><title>DotNetBrowser 2.12</title><link>https://teamdev.com/dotnetbrowser/releases/2022/v2-12/</link><pubDate>Wed, 23 Mar 2022 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2022/v2-12/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium-98" data-title>
Chromium 98&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-98
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>The Chromium engine has been upgraded to version 98.0.4758.102.&lt;/p>
&lt;p>This Chromium version includes many &lt;a href="https://chromereleases.googleblog.com/2022/02/stable-channel-update-for-desktop_14.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>security fixes&lt;/a>, so we recommend that you upgrade to this version.&lt;/p>
&lt;h3 id="ime-support" data-title>
IME support&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#ime-support
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Now, you can enter text in Chinese, Japanese, Korean, etc. using IME in the off-screen rendering mode both in WPF and WinForms applications.&lt;/p></description></item><item><title>DotNetBrowser 2.11</title><link>https://teamdev.com/dotnetbrowser/releases/2022/v2-11/</link><pubDate>Fri, 14 Jan 2022 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2022/v2-11/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium-96" data-title>
Chromium 96&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-96
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Chromium has been upgraded to version 96.0.4664.110.&lt;/p>
&lt;p>This Chromium version &lt;a href="https://chromereleases.googleblog.com/2021/12/stable-channel-update-for-desktop_13.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>includes&lt;/a> 5 security fixes, so we recommend that you upgrade to this version.&lt;/p>
&lt;h3 id="intercepting-touch-events" data-title>
Intercepting touch events&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#intercepting-touch-events
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>It is now possible to handle touch events using the following handlers: &lt;code>Touch.Started.Handler&lt;/code>, &lt;code>Touch.Moved.Handler&lt;/code>, &lt;code>Touch.Canceled.Handler&lt;/code> and &lt;code>Touch.Ended.Handler&lt;/code>. See example below:&lt;/p></description></item><item><title>DotNetBrowser 2.10</title><link>https://teamdev.com/dotnetbrowser/releases/2021/v2-10/</link><pubDate>Thu, 18 Nov 2021 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2021/v2-10/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium-94" data-title>
Chromium 94&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-94
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Chromium has been upgraded to version 94.0.4606.113.&lt;/p>
&lt;p>In March 2021, Google announced that Chrome/Chromium is planning to release a new milestone every 4 weeks, starting with Chrome/Chromium 94 in Q3 of 2021. Additionally, they added a new Extended Stable option, with milestone updates every 8 weeks. Security updates on Extended Stable will be released every two weeks to fix important issues, however, those updates won’t contain new features or all security fixes that the 4-week option will receive.&lt;/p></description></item><item><title>DotNetBrowser 2.9</title><link>https://teamdev.com/dotnetbrowser/releases/2021/v2-9/</link><pubDate>Fri, 24 Sep 2021 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2021/v2-9/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium-92" data-title>
Chromium 92&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-92
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>The Chromium engine has been upgraded to version 92.0.4515.159.&lt;/p>
&lt;h3 id="load-progress-event" data-title>
Load progress event&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#load-progress-event
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>The &lt;code>INavigation&lt;/code> interface has been extended with the &lt;code>LoadProgressChanged&lt;/code> event. It allows getting notifications about load progress:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-csharp" data-lang="csharp">&lt;span class="line">&lt;span class="cl">&lt;span class="n">browser&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Navigation&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">LoadProgressChanged&lt;/span> &lt;span class="p">+=&lt;/span> &lt;span class="p">(&lt;/span>&lt;span class="n">s&lt;/span>&lt;span class="p">,&lt;/span> &lt;span class="n">e&lt;/span>&lt;span class="p">)&lt;/span> &lt;span class="p">=&amp;gt;&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="p">{&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="c1">//The value indicating the loading progress of the web page.&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="kt">double&lt;/span> &lt;span class="n">progress&lt;/span> &lt;span class="p">=&lt;/span> &lt;span class="n">e&lt;/span>&lt;span class="p">.&lt;/span>&lt;span class="n">Progress&lt;/span>&lt;span class="p">;&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="p">};&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h3 id="mouse-events" data-title>
Mouse events&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#mouse-events
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>We added the recognition of the additional (back/forward) mouse buttons. Here is how you can use the new feature to suppress the corresponding mouse events, for example:&lt;/p></description></item><item><title>DotNetBrowser 2.8</title><link>https://teamdev.com/dotnetbrowser/releases/2021/v2-8/</link><pubDate>Fri, 20 Aug 2021 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2021/v2-8/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium-91" data-title>
Chromium 91&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-91
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>In this version, we upgraded Chromium to version 91.0.4472.164 that includes &lt;a href="https://chromereleases.googleblog.com/2021/07/stable-channel-update-for-desktop.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>8 important security fixes&lt;/a>.&lt;/p>
&lt;h3 id="network-connection-state" data-title>
Network connection state&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#network-connection-state
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Now you can get notifications when the network connection state is changed.&lt;/p>
&lt;p>Chromium internally tracks the Internet connection status. When the Internet connection is dropped and then restored, Chromium detects this and programmatically reloads the currently loaded web page.&lt;/p></description></item><item><title>DotNetBrowser 2.7</title><link>https://teamdev.com/dotnetbrowser/releases/2021/v2-7/</link><pubDate>Mon, 26 Jul 2021 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2021/v2-7/</guid><description>&lt;div class="note-block lead">
&lt;p>New DotNetBrowser 2.7 brings an updated Chromium engine and the API with new functionality.&lt;/p>
&lt;/div>
&lt;h2 id="whats-new" data-title>
What’s new&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium-91" data-title>
Chromium 91&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-91
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>The Chromium engine has been updated to version 91.0.4472.114.&lt;/p>
&lt;p>This Chromium version includes several important &lt;a href="https://chromereleases.googleblog.com/2021/06/stable-channel-update-for-desktop_17.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>security fixes&lt;/a>, so we recommend that you upgrade to this version.&lt;/p>
&lt;p>Some of the Chromium features wrapped with the DotNetBrowser have been removed or changed. Check out the &lt;a href="https://teamdev.com/dotnetbrowser/migration/within-v2/v2-6-v2-7/"
>migration guide&lt;/a> to see what DotNetBrowser API has been removed and what alternatives you should use instead.&lt;/p></description></item><item><title>DotNetBrowser 2.6</title><link>https://teamdev.com/dotnetbrowser/releases/2021/v2-6/</link><pubDate>Thu, 27 May 2021 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2021/v2-6/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 2.6 is available for download. In this update the Chromium engine has been upgraded to version 90.&lt;/p>
&lt;/div>
&lt;h2 id="whats-new" data-title>
What’s New&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium-90" data-title>
Chromium 90&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-90
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>In this release of DotNetBrowser, the Chromium engine has been updated to version 90.0.4430.93. This Chromium build includes several important &lt;a href="https://chromereleases.googleblog.com/2021/04/stable-channel-update-for-desktop_26.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>security fixes&lt;/a>, so we recommend that you upgrade to this version.&lt;/p></description></item><item><title>DotNetBrowser 2.5</title><link>https://teamdev.com/dotnetbrowser/releases/2021/v2-5/</link><pubDate>Wed, 07 Apr 2021 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2021/v2-5/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 2.5 is based on Chromium 88.&lt;/p>
&lt;/div>
&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s New&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium-88" data-title>
Chromium 88&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-88
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Chromium engine in DotNetBrowser 2.5 has been updated to version 88.0.4324.182.
&lt;br>
&lt;br>
In this Chromium build some of its features wrapped with the DotNetBrowser have been removed or changed, so this DotNetBrowser version introduces several breaking changes in the public API.
Check out the &lt;a href="https://teamdev.com/dotnetbrowser/migration/within-v2/v2-4-v2-5/"
>migration guide&lt;/a> for this version to see what API has been changed/removed and what alternatives you should use instead.&lt;/p></description></item><item><title>DotNetBrowser 2.4</title><link>https://teamdev.com/dotnetbrowser/releases/2021/v2-4/</link><pubDate>Tue, 02 Mar 2021 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2021/v2-4/</guid><description>&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s New&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="printing-api" data-title>
Printing API&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#printing-api
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>The Printing API is back – improved and redesigned. Now you can print pages and documents as well as savе web pages to PDF silently from the code.&lt;/p>
&lt;p>With the new Printing API you can:&lt;/p>
&lt;ul>
&lt;li>select a printer device;&lt;/li>
&lt;li>provide the required print settings such as paper size, orientation, page ranges, etc.;&lt;/li>
&lt;li>get notifications when printing is completed;&lt;/li>
&lt;li>cancel printing;&lt;/li>
&lt;li>save the currently loaded web page to a PDF document and more.&lt;/li>
&lt;/ul>
&lt;p>The following example demonstrates how to save the currently loaded web page as a PDF:&lt;/p></description></item><item><title>DotNetBrowser 2.3</title><link>https://teamdev.com/dotnetbrowser/releases/2020/v2-3/</link><pubDate>Thu, 26 Nov 2020 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2020/v2-3/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 2.3 is based on Chromium 84.&lt;/p>
&lt;/div>
&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s New&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium-84" data-title>
Chromium 84&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-84
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>Chromium has been updated to version 84.0.4147.135.&lt;/p>
&lt;div class="note-block note">
&lt;p>In this Chromium build some of its features wrapped with the DotNetBrowser have been removed or changed, so this DotNetBrowser version introduces several breaking changes in the public API.
&lt;br>
&lt;br>
Check out the &lt;a href="https://teamdev.com/dotnetbrowser/migration/within-v2/v2-2-v2-3/"
>migration guide&lt;/a> for this version to see what API has been changed/removed and what alternatives you should use instead.&lt;/p></description></item><item><title>DotNetBrowser 2.2</title><link>https://teamdev.com/dotnetbrowser/releases/2020/v2-2/</link><pubDate>Wed, 09 Sep 2020 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2020/v2-2/</guid><description>&lt;div class="note-block lead">
&lt;p>In this update we improved the rendering performance in the off-screen rendering mode, restored functionality that allows disabling the internal Chromium traffic, and extended your options in managing data and user interaction with the browser.&lt;/p>
&lt;/div>
&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s New&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="rendering-performance" data-title>
Rendering Performance&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#rendering-performance
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>The off-screen rendering performance has been improved on all supported platforms and UI toolkits.&lt;/p>
&lt;p>The results of the rendering performance testing on the different platforms on an HTML5 video in Frame Per Second (FPS) are the following:&lt;/p></description></item><item><title>DotNetBrowser 2.1.1</title><link>https://teamdev.com/dotnetbrowser/releases/2020/v2-1-1/</link><pubDate>Thu, 02 Jul 2020 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2020/v2-1-1/</guid><description>&lt;div class="note-block lead">
&lt;p>This minor update brings improved searching assemblies algorithm for the Global Assembly Cache.&lt;/p>
&lt;/div>
&lt;h2 id="improvement" data-title>
Improvement&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#improvement
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Updated searching assemblies algorithm for the Global Assembly Cache.&lt;/li>
&lt;/ul>
&lt;h2 id="fixed-issues" data-title>
Fixed issues&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#fixed-issues
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>&lt;code>InvalidOperationException&lt;/code>: &amp;ldquo;This Visual is not connected to a PresentationSource.&amp;rdquo; thrown when moving, minimizing or maximizing a BrowserView control in WPF applications in both rendering modes.&lt;/li>
&lt;li>Unpredictable behavior when using BrowserView controls inside TabControls or equivalent.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 2.1</title><link>https://teamdev.com/dotnetbrowser/releases/2020/v2-1/</link><pubDate>Thu, 18 Jun 2020 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2020/v2-1/</guid><description>&lt;div class="note-block lead">
&lt;p>This update enhances the DotNetBrowser with possibilities of the Chromium 79 and a range of features, adding to the convenience of interaction with the library.&lt;/p>
&lt;/div>
&lt;h2 id="whats-new" data-title>
What&amp;rsquo;s New&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#whats-new
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;h3 id="chromium-79" data-title>
Chromium 79&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-79
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>The Chromium engine has been upgraded to version &lt;code>79.0.3945.130&lt;/code>.&lt;/p>
&lt;h3 id="access-to-engine-options" data-title>
Access to Engine options&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#access-to-engine-options
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h3>
&lt;p>It got possible to access the Engine options when two or more &lt;code>Engine&lt;/code> instances run simultaneously. Now you can easily customize the Engine language, rendering mode and &lt;a href="https://teamdev.com/dotnetbrowser/docs/guides/gs/engine/#engine-options"
>much more&lt;/a>.&lt;/p></description></item><item><title>DotNetBrowser 2.0</title><link>https://teamdev.com/dotnetbrowser/releases/2020/v2/</link><pubDate>Thu, 27 Feb 2020 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2020/v2/</guid><description>&lt;div class="note-block lead">
&lt;p>Please meet a major update of DotNetBrowser &amp;mdash; version 2.0! It introduces fundamental changes to the public API of the library allowing lots of new features and space for further growth.&lt;/p>
&lt;/div>
&lt;p>We have improved the library implementation to make it compatible with .NET Standard 2.0. As a result, DotNetBrowser 2.0 supports .NET Core 2.2 as well as 3.0 on Windows.&lt;/p>
&lt;p>The new version requires .NET Framework 4.5 or higher.&lt;/p></description></item><item><title>DotNetBrowser 1.21.5</title><link>https://teamdev.com/dotnetbrowser/releases/2020/v1-21-5/</link><pubDate>Tue, 25 Feb 2020 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2020/v1-21-5/</guid><description>&lt;p>The new version comes with an important fix, that resolves the blocker issue with the &lt;code>TypeLoadException&lt;/code>, which occurs on runtime if the DotNetBrowser64.dll is used in the project.&lt;/p>
&lt;p>We strongly recommend that you use version 1.21.5 instead of 1.21.4.&lt;/p>
&lt;p>&lt;a href="https://teamdev.com/dotnetbrowser#evaluate"
>Request evaluation licence&lt;/a>&lt;/p></description></item><item><title>DotNetBrowser 1.21.4</title><link>https://teamdev.com/dotnetbrowser/releases/2020/v1-21-4/</link><pubDate>Mon, 24 Feb 2020 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2020/v1-21-4/</guid><description>&lt;p>This library update provides fix for the improper location of the IME input when using the Chinese language.&lt;/p>
&lt;p>&lt;a href="https://teamdev.com/dotnetbrowser#evaluate"
>Request evaluation licence&lt;/a>&lt;/p></description></item><item><title>DotNetBrowser 1.21.3</title><link>https://teamdev.com/dotnetbrowser/releases/2020/v1-21-3/</link><pubDate>Tue, 11 Feb 2020 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2020/v1-21-3/</guid><description>&lt;p>With this update the library gets more apt for localization and remote desktop operation.&lt;/p>
&lt;h2 id="fixed-issues" data-title>
Fixed issues&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#fixed-issues
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>The InvalidOperationException error occurring, when a window with the WPFBrowserView control in the heavyweight rendering mode is used via a remote desktop connection.&lt;/li>
&lt;li>The JSValue returning a wrong number value in the German culture.&lt;/li>
&lt;/ul>
&lt;p>&lt;a href="https://teamdev.com/dotnetbrowser#evaluate"
>Request evaluation licence&lt;/a>&lt;/p></description></item><item><title>DotNetBrowser 1.21.2</title><link>https://teamdev.com/dotnetbrowser/releases/2019/v1-21-2/</link><pubDate>Wed, 25 Dec 2019 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2019/v1-21-2/</guid><description>&lt;div class="note-block lead">
&lt;p>With this release the library gets more stable due to some important fixes.&lt;/p>
&lt;/div>
&lt;h2 id="fixed-issues" data-title>
Fixed issues:&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#fixed-issues
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>The NullReferenceException error, occurring, when a window with the WPFBrowserView control in the lightweight rendering mode is moved.&lt;/li>
&lt;li>The native process crashing if the LoadHandler.OnLoad method returns true.&lt;/li>
&lt;/ul>
&lt;p>&lt;a href="https://teamdev.com/dotnetbrowser#evaluate"
>Request evaluation licence&lt;/a>&lt;/p></description></item><item><title>DotNetBrowser 1.21.1</title><link>https://teamdev.com/dotnetbrowser/releases/2019/v1-21-1/</link><pubDate>Thu, 24 Oct 2019 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2019/v1-21-1/</guid><description>&lt;h2 id="improvements" data-title>
Improvements:&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#improvements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>We have added the sign to the GZipCompress.exe utility, which will reduce the number of errors with firewalls, antiviruses and other security software, when launching applications, containing DotNetBrowser.&lt;/li>
&lt;li>The embedding process of the &lt;code>WinFormsBrowserView&lt;/code> component in a WPF application got better. Now pop up windows are available upon embedding.&lt;/li>
&lt;/ul>
&lt;h2 id="fixed-issues" data-title>
Fixed issues:&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#fixed-issues
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>The InvalidCastException occurring because of the new &lt;code>PermissionRequest.PermissionType&lt;/code> values in Chromium 69.&lt;/li>
&lt;li>The InvalidOperationException occurring with the Channel already closed exception if registering a protocol handler for two or more &lt;code>BrowserContext&lt;/code> instances.&lt;/li>
&lt;/ul>
&lt;p>&lt;a href="https://teamdev.com/dotnetbrowser#evaluate"
>Request evaluation licence&lt;/a>&lt;/p></description></item><item><title>DotNetBrowser 1.21</title><link>https://teamdev.com/dotnetbrowser/releases/2019/v1-21/</link><pubDate>Tue, 20 Aug 2019 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2019/v1-21/</guid><description>&lt;div class="note-block lead">
&lt;p>The new version of DotNetBrowser introduces a number of requested features, and fixes making the library work even smoother:&lt;/p>
&lt;/div>
&lt;h2 id="certificate-chain" data-title>
Certificate chain&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#certificate-chain
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>The &lt;code>CertificateVerifyParams.IntermediateCertificates&lt;/code> property allows getting the intermediate certificate list retrieved from the server that can be used to reconstruct and verify the complete certificate chain.&lt;/p>
&lt;h2 id="disable-form-autofill-functionality" data-title>
Disable form autofill functionality&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#disable-form-autofill-functionality
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>The &lt;code>BrowserContext.AutoFillEnabled&lt;/code> property allows enabling or disabling auto-fill functionality.&lt;/p></description></item><item><title>DotNetBrowser 1.20.1</title><link>https://teamdev.com/dotnetbrowser/releases/2019/v1-20-1/</link><pubDate>Tue, 11 Jun 2019 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2019/v1-20-1/</guid><description>&lt;div class="note-block lead">
&lt;p>New version features several important improvements adding up to the library&amp;rsquo;s convenience and productivity:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Now you can easily check if the binaries use proprietary codecs with the new &lt;code>ChromiumBinaries.IsCodecEnabled&lt;/code> property.&lt;/li>
&lt;li>It got simple to look the Chromium version up – just check the Product version property of assemblies.&lt;/li>
&lt;li>Use DotNetBrowser conveniently with toolbox support for Visual Studio 2019.&lt;/li>
&lt;li>The new dispose logic allows the instance not to wait until all separated threads are released after invoking &lt;code>Browser.Dispose()&lt;/code> or &lt;code>BrowserView.Dispose()&lt;/code> methods.&lt;/li>
&lt;li>We have also improved the algorithm for unpacking the Chromium binaries.&lt;/li>
&lt;/ul>
&lt;p>Fixed Issues:&lt;/p></description></item><item><title>DotNetBrowser 1.20</title><link>https://teamdev.com/dotnetbrowser/releases/2019/v1-20/</link><pubDate>Sat, 20 Apr 2019 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2019/v1-20/</guid><description>&lt;div class="note-block lead">
&lt;p>This version allows you to:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Display web pages more accurately, play MP3 audio, and easily set up printing across devices with new Chromium.&lt;/li>
&lt;li>Protect your application from security breaches with fix to &lt;strong>CVE-2019-5786&lt;/strong> Chrome vulnerability&lt;/li>
&lt;li>Simulate complex real-life user interactions with key modifiers for simulated mouse events.&lt;/li>
&lt;li>Timely track down errors of proxy in Chromium.&lt;/li>
&lt;li>Define current Chromium version used in your application.&lt;/li>
&lt;/ul>
&lt;h2 id="chromium-69" data-title>
Chromium 69&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-69
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>The Chromium engine has been upgraded to version 69.0.3497.12. Here are a few of its helpful features:&lt;/p></description></item><item><title>DotNetBrowser 1.19.1</title><link>https://teamdev.com/dotnetbrowser/releases/2019/v1-19-1/</link><pubDate>Mon, 14 Jan 2019 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2019/v1-19-1/</guid><description>&lt;div class="note-block lead">
&lt;p>This minor update of the library contains a number of improvements and fixes.&lt;/p>
&lt;/div>
&lt;h2 id="fixes" data-title>
Fixes:&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#fixes
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>The offset issue with 101-124 DPI setting when using the &lt;code>WPFBrowserView&lt;/code> instance in the heavyweight rendering mode.&lt;/li>
&lt;li>The disposal of the &lt;code>Browser&lt;/code> and &lt;code>BrowserView&lt;/code> instances in different AppDomains.&lt;/li>
&lt;/ul>
&lt;h2 id="improvements" data-title>
Improvements:&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#improvements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>The extraction logic has been improved. Now, the Chromium 32-bit and 64-bit binaries are extracted to the different directories.&lt;/li>
&lt;li>Mask passwords in the log messages.&lt;/li>
&lt;/ul>
&lt;p>&lt;a href="https://teamdev.com/dotnetbrowser#evaluate"
>Request evaluation licence&lt;/a>&lt;/p></description></item><item><title>DotNetBrowser 1.19</title><link>https://teamdev.com/dotnetbrowser/releases/2018/v1-19/</link><pubDate>Tue, 27 Nov 2018 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2018/v1-19/</guid><description>&lt;div class="note-block lead">
&lt;p>The new version of DotNetBrowser got more flexible and stable due to the following changes:&lt;/p>
&lt;/div>
&lt;h2 id="browserdisposebool-checkbeforeunload-implemented" data-title>
Browser.Dispose(bool checkBeforeUnload) Implemented&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#browserdisposebool-checkbeforeunload-implemented
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>Due to this method, it got possible to invoke the &lt;code>DialogHandler.OnBeforeUnload&lt;/code> method which is fired if the web page contains the &lt;code>onbeforeunload&lt;/code> JavaScript event.&lt;/p>
&lt;h2 id="filechooserparamsfilter-introduced" data-title>
FileChooserParams.Filter Introduced&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#filechooserparamsfilter-introduced
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>This property provides a meaningful description of the file extensions accepted by the file chooser. This information comes from the accept attribute of the input HTML element with the &lt;code>type=file&lt;/code> attribute.&lt;/p></description></item><item><title>DotNetBrowser 1.18</title><link>https://teamdev.com/dotnetbrowser/releases/2018/v1-18/</link><pubDate>Mon, 08 Oct 2018 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2018/v1-18/</guid><description>&lt;div class="note-block lead">
&lt;p>The new DotNetBrowser comes with the following new features:&lt;/p>
&lt;/div>
&lt;h2 id="chromium-64-bit-process-support" data-title>
Chromium 64-bit process support&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-64-bit-process-support
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>DotNetBrowser distribution package now includes both Chromium 64-bit and 32-bit binaries.&lt;/p>
&lt;p>&lt;strong>Important:&lt;/strong> Please note that Chromium 64-bit binaries can be used only on Windows 64-bit and cannot be used on Windows 32-bit.&lt;/p>
&lt;h2 id="clear-http-basic-authentication-cache" data-title>
Clear HTTP (basic) authentication cache&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#clear-http-basic-authentication-cache
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>The API has been extended with new functionality that allows clearing HTTP Auth cache.&lt;br>&lt;/p></description></item><item><title>DotNetBrowser 1.17</title><link>https://teamdev.com/dotnetbrowser/releases/2018/v1-17/</link><pubDate>Fri, 31 Aug 2018 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2018/v1-17/</guid><description>&lt;div class="note-block lead">
&lt;p>Summer months were quite fruitful for DotNetBrowser. Here comes several new features:&lt;/p>
&lt;/div>
&lt;h2 id="default-zoom-level" data-title>
Default zoom level&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#default-zoom-level
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>It is now possible to set the default zoom level for the &lt;code>BrowserContext&lt;/code> instance during its creation. This property allows you to specify the default zoom level for all browsers which use the same context. All pages which are loaded through these &lt;code>Browser&lt;/code> instances will have the specified zoom level from the start.&lt;/p></description></item><item><title>DotNetBrowser 1.16</title><link>https://teamdev.com/dotnetbrowser/releases/2018/v1-16/</link><pubDate>Fri, 29 Jun 2018 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2018/v1-16/</guid><description>&lt;div class="note-block lead">
&lt;p>New version of DotNetBrowser comes with a whole bunch of useful changes:&lt;/p>
&lt;/div>
&lt;h2 id="hidpi-displays" data-title>
HiDPI Displays&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#hidpi-displays
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>In this version, we are glad to introduce the HiDPI Displays support which allows using all DPI-aware modes. The &lt;code>BrowserView&lt;/code> control is compatible with various DPI awareness modes and renders HTML content with respect to the scale factor.&lt;/p>
&lt;h2 id="fips-compliance" data-title>
FIPS-compliance&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#fips-compliance
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>We are FIPS-compliant now! Starting from the version 1.16, it is possible to use DotNetBrowser in the environments where the Federal Information Processing Standard restriction is enabled.&lt;/p></description></item><item><title>DotNetBrowser 1.15</title><link>https://teamdev.com/dotnetbrowser/releases/2018/v1-15/</link><pubDate>Mon, 04 Jun 2018 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2018/v1-15/</guid><description>&lt;div class="note-block lead">
&lt;p>Good news everyone! Chromium version was upgraded in the new DotNetBrowser!&lt;/p>
&lt;/div>
&lt;h2 id="chromium-64" data-title>
Chromium 64&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-64
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>The Chromium engine has been upgraded to version 64.0.3282.24.&lt;/p>
&lt;h2 id="improvements" data-title>
Improvements:&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#improvements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>The Printing API has been extended with the new color models.&lt;/p>
&lt;h2 id="fixed-issues" data-title>
Fixed issues:&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#fixed-issues
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>The Chromium profile directory being unlocked while there are alive &lt;code>Browser&lt;/code> instances related to the corresponding context.&lt;/li>
&lt;li>The ArgumentNullException exception during raising the &lt;code>PreviewKeyDown&lt;/code> event.&lt;/li>
&lt;li>Render process crash during disposing &lt;code>Browser&lt;/code> instances.&lt;/li>
&lt;/ul>
&lt;p>&lt;a href="https://teamdev.com/dotnetbrowser#evaluate"
>Request evaluation licence&lt;/a>&lt;/p></description></item><item><title>DotNetBrowser 1.14.3</title><link>https://teamdev.com/dotnetbrowser/releases/2018/v1-14-3/</link><pubDate>Wed, 16 May 2018 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2018/v1-14-3/</guid><description>&lt;p>In this minor update all binary files are signed with an updated certificate.&lt;/p>
&lt;p>The certificate, we used to sign binary files in DotNetBrowser 1.14.2 and lower, already expired. So, if you need to use DotNetBrowser in an environment where it&amp;rsquo;s required that all binary files including exe and dll are signed with a valid certificate, then we strongly recommend that you upgrade to 1.14.3.&lt;/p>
&lt;p>&lt;a href="https://teamdev.com/dotnetbrowser#evaluate"
>Request evaluation licence&lt;/a>&lt;/p></description></item><item><title>DotNetBrowser 1.14.2</title><link>https://teamdev.com/dotnetbrowser/releases/2018/v1-14-2/</link><pubDate>Wed, 11 Apr 2018 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2018/v1-14-2/</guid><description>&lt;p>New DotNetBrowser comes with an important fix that resolves the blocker issue in the IPC module introduced in DotNetBrowser 1.14.1.&lt;/p>
&lt;p>We strongly recommend that you use 1.14.2 instead of 1.14.1.&lt;/p>
&lt;p>&lt;a href="https://teamdev.com/dotnetbrowser#evaluate"
>Request evaluation licence&lt;/a>&lt;/p></description></item><item><title>DotNetBrowser 1.14.1</title><link>https://teamdev.com/dotnetbrowser/releases/2018/v1-14-1/</link><pubDate>Tue, 10 Apr 2018 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2018/v1-14-1/</guid><description>&lt;p>&lt;strong>Important:&lt;/strong> this version contains a blocker issue that has been fixed in 1.14.2. Please use 1.14.2 instead of 1.14.1.&lt;/p>
&lt;div class="note-block lead">
&lt;p>Current release is focused on creating solutions for reported issues, and improving performance of some key areas:&lt;/p>
&lt;/div>
&lt;h2 id="improvements" data-title>
Improvements&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#improvements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>The available port detection algorithm during the socket initialization is improved.&lt;/li>
&lt;li>Logging is improved.&lt;/li>
&lt;li>The &lt;code>Browser.OnStartLoadingFrame&lt;/code> and &lt;code>Browser.OnProvisionalLoadingFrame&lt;/code> events is improved.&lt;/li>
&lt;li>The VS 2017 VSIX package compatibility is added.&lt;/li>
&lt;/ul>
&lt;h2 id="fixed-issues" data-title>
Fixed issues&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#fixed-issues
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>DotNetBrowser WPF visual component raising an error in the Design mode. This issue was caused by the &lt;code>WPFBrowserView()&lt;/code> constructor implementation.&lt;/li>
&lt;li>&lt;code>Browser&lt;/code> or &lt;code>BrowserView&lt;/code> instance hanging in the different AppDomains. This issue was caused by an issue in the internal IPC module.&lt;/li>
&lt;li>InvalidOperationException exception with the &amp;ldquo;Channel is already closed&amp;rdquo; message being thrown. This issue was caused by the native crash in the Chromium render process.&lt;/li>
&lt;li>&lt;code>BrowserPreferences.SetChromiumDir()&lt;/code> method having no effect on the Release configuration. The issue was related to the inline initialization of the static fields.&lt;/li>
&lt;li>Some events not being present in the WinForms Properties window in the Design mode. This issue was caused by the lack of the event attributes.&lt;/li>
&lt;li>Custom &lt;code>NetworkDelegate&lt;/code> not working after all the &lt;code>Browser&lt;/code> or &lt;code>BrowserView&lt;/code> instances are disposed and created again. This issue was caused by an issue in the &lt;code>NetworkService&lt;/code> implementation.&lt;/li>
&lt;li>The issue with incorrect &lt;code>WPFBrowserView&lt;/code> location hosted in &lt;code>ElementHost&lt;/code>.&lt;/li>
&lt;li>The issue with displaying mouse cursor &lt;code>WinFormsBrowserView&lt;/code>.&lt;/li>
&lt;li>The issue with focus stealing on every navigation.&lt;/li>
&lt;li>The native crash when disposing &lt;code>Browser&lt;/code>instance when printing is in progress.&lt;/li>
&lt;li>The issue when &lt;code>BrowserView.GetImage()&lt;/code> returns black rectangle.&lt;/li>
&lt;li>The issue when &lt;code>ProtocolService.Unregister(IProtocolHandler)&lt;/code> method removes all protocols.&lt;/li>
&lt;/ul>
&lt;p>&lt;a href="https://teamdev.com/dotnetbrowser#evaluate"
>Request evaluation licence&lt;/a>&lt;/p></description></item><item><title>DotNetBrowser 1.14</title><link>https://teamdev.com/dotnetbrowser/releases/2017/v1-14/</link><pubDate>Thu, 30 Nov 2017 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2017/v1-14/</guid><description>&lt;div class="note-block lead">
&lt;p>With this DotNetBrowser update we focused on enhancements for browsing privacy, and HTML5 handling.&lt;/p>
&lt;/div>
&lt;h2 id="incognito-mode" data-title>
Incognito Mode&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#incognito-mode
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>By default, each &lt;code>Browser&lt;/code> instance stores all user data such as history, cookies, cache on the disk. Starting from version 1.14, you can configure &lt;code>Browser&lt;/code> to store all user data in memory (Chromium&amp;rsquo;s &amp;ldquo;Incognito&amp;rdquo; mode), so that all user data will be cleared once your .NET application is terminated.&lt;/p></description></item><item><title>DotNetBrowser 1.13</title><link>https://teamdev.com/dotnetbrowser/releases/2017/v1-13/</link><pubDate>Wed, 18 Oct 2017 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2017/v1-13/</guid><description>&lt;p>This version of the library was extended with the features, allowing to intercept all the URL requests for both standard URL schemes (such as http, https, ftp, file), and custom schemes declared in your application. After registering a protocol handler for a scheme, all the URLs with the specified scheme loaded into the Browser will be handled by this handler.&lt;/p>
&lt;h2 id="protocol-handler" data-title>
Protocol Handler&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#protocol-handler
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>Implementing a new custom protocol handler in DotNetBrowser is pretty simple:&lt;/p></description></item><item><title>DotNetBrowser 1.12</title><link>https://teamdev.com/dotnetbrowser/releases/2017/v1-12/</link><pubDate>Wed, 20 Sep 2017 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2017/v1-12/</guid><description>&lt;div class="note-block lead">
&lt;p>We are happy to announce availability of the new DotNetBrowser version. Please find a detailed overview of the changes, introduced in v1.12:&lt;/p>
&lt;/div>
&lt;h2 id="chromium-60" data-title>
Chromium 60&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#chromium-60
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>The Chromium engine was upgraded to version 60.0.3112.113. It means that support of WebGL 2.0 was automatically enabled.&lt;/p>
&lt;h2 id="new-features" data-title>
New features&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#new-features
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Ability to modify &lt;code>User-Agent&lt;/code> string for the particular &lt;code>Browser&lt;/code> instance at runtime.&lt;br>&lt;/li>
&lt;li>Ability to change &lt;code>AcceptLanguage&lt;/code> for the particular Browser instance at runtime.&lt;br>&lt;/li>
&lt;li>Ability to convert JSObject to JSON string.&lt;/li>
&lt;/ul>
&lt;h2 id="improvements" data-title>
Improvements&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#improvements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>The on-screen keyboard support in Windows 10.&lt;/li>
&lt;li>Support of custom cursors (WPF, Lightweight). The previous implementation created undesired temporary files in the working directory. Such behavior may have caused exceptions when the working directory is read-only.&lt;/li>
&lt;li>The startup errors handling. Now the exceptions that may be thrown during startup will include more information about the root cause of the error.&lt;/li>
&lt;li>Stability when loading Flash content after displaying a PDF file.&lt;/li>
&lt;li>Stability when loading Flash content after displaying popups.&lt;/li>
&lt;/ul>
&lt;h2 id="fixed-issues" data-title>
Fixed issues:&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#fixed-issues
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>The &lt;code>WPFBrowserView.PreviewMouseWheel&lt;/code> event now provides the scroll delta properly (WPF, Heavyweight). In the previous implementation, the received scroll delta was always set to 0.&lt;/li>
&lt;li>Issue with custom &lt;code>PopupHandler&lt;/code> implementation being ignored and the default one being used when the &lt;code>WPFBrowserView&lt;/code> control is hosted in the WinForms applications.&lt;/li>
&lt;li>Unnecessary focus grabbing when the &lt;code>StartLoadingFrameEvent&lt;/code> event has been received (WPF, Heavyweight).&lt;/li>
&lt;li>Issue when it&amp;rsquo;s not possible to access some properties of the &lt;code>IDictionary&lt;/code> object injected into JavaScript through JS-.NET bridge API. For example, the previous implementation worked improperly with the Keys property.&lt;/li>
&lt;li>Losing keyboard focus after displaying a JavaScript dialog (WinForms, Lightweight).&lt;/li>
&lt;li>Blurred text on a web page (WPF, WinForms, Lightweight).&lt;/li>
&lt;li>PDF document rendered incorrectly in the environments with non-default DPI settings.&lt;/li>
&lt;/ul>
&lt;p>&lt;a href="https://teamdev.com/dotnetbrowser#evaluate"
>Request evaluation licence&lt;/a>&lt;/p></description></item><item><title>DotNetBrowser 1.11.1</title><link>https://teamdev.com/dotnetbrowser/releases/2017/v1-11-1/</link><pubDate>Mon, 14 Aug 2017 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2017/v1-11-1/</guid><description>&lt;div class="note-block lead">
&lt;p>Resolved issues:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>&lt;code>DownloadHandler&lt;/code> not working if the DotNetBrowser assembly was loaded via &lt;code>Assembly.Load()&lt;/code>.&lt;/li>
&lt;li>Sporadic Chromium crash for &lt;code>BrowserView&lt;/code> running in the lightweight mode.&lt;/li>
&lt;li>.NET memory leak in the ImageProvider implementation.&lt;/li>
&lt;li>&lt;code>WPFBrowserView&lt;/code> focus stealing issue (reproducible for WPF ToolBar buttons in the same window).&lt;/li>
&lt;/ul>
&lt;p>&lt;a href="https://teamdev.com/dotnetbrowser#evaluate"
>Request evaluation licence&lt;/a>&lt;/p></description></item><item><title>DotNetBrowser 1.11</title><link>https://teamdev.com/dotnetbrowser/releases/2017/v1-11/</link><pubDate>Mon, 26 Jun 2017 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2017/v1-11/</guid><description>&lt;div class="note-block lead">
&lt;p>Please meet a new, more functional and stable version of DotNetBrowser. This update contains:&lt;/p>
&lt;/div>
&lt;h2 id="new-features" data-title>
New features&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#new-features
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Taking page screenshot without creating &lt;code>BrowserView&lt;/code>. With this feature, it is possible to take screenshots of the loaded web page having only &lt;code>Browser&lt;/code> instance. This feature works only if the &lt;code>Browser&lt;/code> was created in the lightweight rendering mode.&lt;/li>
&lt;li>Touch event handling. Now it is possible to intercept touch events and prevent them from being handled by the Chromium engine.&lt;/li>
&lt;li>Unpacking Chromium binaries to the the non-default folder.&lt;/li>
&lt;li>Ability to provide a custom CA certificate.&lt;/li>
&lt;li>Extended drag and drop events, which provide the ability to access the underlying &lt;code>IDataObject&lt;/code> instance.&lt;/li>
&lt;/ul>
&lt;h2 id="resolved-issues" data-title>
Resolved issues&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#resolved-issues
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Incorrect HTML5 application cache behavior when offline.&lt;/li>
&lt;li>An issue with missing JavaScript context, which was the cause of possible &lt;strong>NullReferenceException&lt;/strong>, when working with JavaScript object and missing &lt;code>ScriptContextCreated&lt;/code> events.
.NET memory leak for synchronous methods.&lt;/li>
&lt;li>KeyPress event handling issue for &lt;code>WinFormsBrowserView&lt;/code> running in the heavyweight rendering mode.&lt;/li>
&lt;/ul>
&lt;h2 id="improvements" data-title>
Improvements&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#improvements
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Removed dependency on Microsoft.VisualStudio.Shell.Immutable.10.0.dll&lt;/li>
&lt;li>Added Chromium profile directory validator to prevent usage of the same data directory by multiple &lt;code>BrowserContext&lt;/code> instances.&lt;/li>
&lt;/ul>
&lt;p>&lt;a href="https://teamdev.com/dotnetbrowser#evaluate"
>Request evaluation licence&lt;/a>&lt;/p></description></item><item><title>DotNetBrowser 1.10</title><link>https://teamdev.com/dotnetbrowser/releases/2017/v1-10/</link><pubDate>Thu, 27 Apr 2017 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2017/v1-10/</guid><description>&lt;div class="note-block lead">
&lt;p>With this release we are pleased to introduce the long awaited upgrade. Now DotNetBrowser runs on a more powerful browser engine – Chromium 55.0.2883.87. But we did not stop there, check the full list of enhancements we delivered with this update:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Implemented Chromium sandbox support. By default, Chromium sandbox is disabled to keep the behavior of previous DotNetBrowser versions.&lt;/li>
&lt;li>The library now supports HTML5 transparent background.&lt;/li>
&lt;li>Added the &lt;code>OnPreviewKeyDown&lt;/code> event support in WinForms heavyweight rendering mode.&lt;/li>
&lt;li>Added support of the proper key modifiers for the keyboard events in WinForms heavyweight rendering mode.&lt;/li>
&lt;li>Implemented an ability to embed WPFBrowserView into WinForms ElementHost.&lt;/li>
&lt;/ul>
&lt;div class="note-block lead">
&lt;p>Here’s what has been resolved in this update:&lt;/p></description></item><item><title>DotNetBrowser 1.9</title><link>https://teamdev.com/dotnetbrowser/releases/2017/v1-9/</link><pubDate>Fri, 03 Feb 2017 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2017/v1-9/</guid><description>&lt;p>Great news for Visual Studio users! DotNetBrowser 1.9 can be used as a web browser component for .NET apps, developed in Visual Studio 2017 RC.&lt;/p>
&lt;p>Apart from Visual Studio 2017 RC support, in this version, we concentrated on extending DOM API with new features, ability to specify custom CSS rules which will be then applied to every loaded web page, enhancements in heavyweight rendering mode, and several other important updates, aimed at improving security and performance of the library.&lt;/p></description></item><item><title>DotNetBrowser 1.8.4</title><link>https://teamdev.com/dotnetbrowser/releases/2016/v1-8-4/</link><pubDate>Mon, 19 Dec 2016 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2016/v1-8-4/</guid><description>&lt;h2 id="new-features" data-title>
New features&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#new-features
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>Desktop notifications and permission request support.&lt;/strong> Now it is possible to handle the case when a web page wants to display desktop notifications or ask for a permission. You decide whether the web page is allowed to display notifications or not. By default, desktop notifications are suppressed.&lt;/li>
&lt;li>Ability to &lt;strong>get the download interruption reason.&lt;/strong> If there is an error during download and the download itself was interrupted, it is possible to obtain the interruption reason (file system, network or server errors).&lt;/li>
&lt;li>Ability to &lt;strong>disable and enable zoom&lt;/strong> for a specific Browser instance to prevent web page from zooming.&lt;/li>
&lt;li>Ability to &lt;strong>force full spell check&lt;/strong> on the web page.&lt;/li>
&lt;/ul>
&lt;h2 id="improvements-in-dom-api" data-title>
Improvements in DOM API&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#improvements-in-dom-api
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>Get XPath of the DOM element.&lt;/strong> Now it is possible to obtain the XPath expression that describes the particular DOM element.&lt;/li>
&lt;li>&lt;strong>Get bounding client rectangle of the DOM element.&lt;/strong> This DOM element property returns the bounds of the element and its position relative to the top-left corner of the current document’s viewport.&lt;/li>
&lt;/ul>
&lt;h2 id="bugfixes" data-title>
Bugfixes&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#bugfixes
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Fixed an issue in the &lt;code>ResourceHandler&lt;/code>. in the previous version, the handler was not working if the network delegate was not configured. Now these two features are working independently.&lt;/li>
&lt;/ul>
&lt;p>&lt;a href="https://teamdev.com/dotnetbrowser#evaluate"
>Request evaluation licence&lt;/a>&lt;/p></description></item><item><title>DotNetBrowser 1.8.3</title><link>https://teamdev.com/dotnetbrowser/releases/2016/v1-8-3/</link><pubDate>Mon, 21 Nov 2016 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2016/v1-8-3/</guid><description>&lt;div class="note-block lead">
&lt;p>We focused on improving the following areas:&lt;/p>
&lt;/div>
&lt;h2 id="performance" data-title>
Performance&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#performance
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Improved page load performance.&lt;/li>
&lt;li>Improved page scrolling smoothness. Now there is no visible delay when scrolling the loaded web page via dragging the scrollbar.&lt;/li>
&lt;/ul>
&lt;h2 id="dom-api" data-title>
DOM API&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#dom-api
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;p>Added the ability to obtain &lt;code>DOMElement&lt;/code> position properties:&lt;/p>
&lt;ul>
&lt;li>&lt;code>DOMElement.OffsetTop&lt;/code>&lt;/li>
&lt;li>&lt;code>DOMElement.OffsetLeft&lt;/code>&lt;/li>
&lt;li>&lt;code>DOMElement.OffsetWidth&lt;/code>&lt;/li>
&lt;li>&lt;code>DOMElement.OffsetHeight&lt;/code>&lt;/li>
&lt;li>&lt;code>DOMElement.ClientTop&lt;/code>&lt;/li>
&lt;li>&lt;code>DOMElement.ClientLeft&lt;/code>&lt;/li>
&lt;li>&lt;code>DOMElement.ClientWidth&lt;/code>&lt;/li>
&lt;li>&lt;code>DOMElement.ClientHeight&lt;/code>&lt;/li>
&lt;li>&lt;code>DOMElement.ScrollTop&lt;/code>&lt;/li>
&lt;li>&lt;code>DOMElement.ScrollLeft&lt;/code>&lt;/li>
&lt;li>&lt;code>DOMElement.ScrollWidth&lt;/code>&lt;/li>
&lt;li>&lt;code>DOMElement.ScrollHeight&lt;/code>&lt;/li>
&lt;/ul>
&lt;h2 id="new-features" data-title>
New Features&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#new-features
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Ability to configure proxy when browser is running. The previous versions of DotNetBrowser allowed to configure proxy settings only once – before creating a &lt;code>Browser&lt;/code> instance. Now it is possible to switch to another proxy without creating a new &lt;code>Browser&lt;/code>.&lt;/li>
&lt;li>HTML5 App Cache support. This type of cache is used by some web applications to make them accessible even without an internet connection.&lt;/li>
&lt;li>Ability to intercept HTTP response and access its contents. The previous versions of DotNetBrowser were able to intercept the requests, but not the responses.&lt;/li>
&lt;/ul>
&lt;h2 id="bugfixes" data-title>
Bugfixes&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#bugfixes
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Fixed keyboard event handling for Windows Forms heavyweight control. In previous versions, the proper key events were not fired for this control.&lt;/li>
&lt;li>Fixed an issue related to processing the &lt;code>User-Agent&lt;/code> string with spaces.&lt;/li>
&lt;/ul>
&lt;p>&lt;a href="https://teamdev.com/dotnetbrowser#evaluate"
>Request evaluation licence&lt;/a>&lt;/p></description></item><item><title>DotNetBrowser 1.8.1</title><link>https://teamdev.com/dotnetbrowser/releases/2016/v1-8-1/</link><pubDate>Tue, 13 Sep 2016 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2016/v1-8-1/</guid><description>&lt;div class="note-block lead">
&lt;p>The new version lists the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>&lt;strong>DOM API update&lt;/strong>, which brings the possibility to modify DOM: create, append, insert, replace and remove DOM nodes.&lt;/li>
&lt;li>Ability to &lt;strong>get the DOM node at the particular location&lt;/strong> on the page.&lt;/li>
&lt;li>Ability to &lt;strong>emulate custom DOM events&lt;/strong> for the specific DOM elements.&lt;/li>
&lt;li>&lt;strong>Mute Audio API.&lt;/strong> This API allows to mute all audio output for the particular &lt;code>Browser&lt;/code> instance. Also, it is possible to determine if the browser is currently muted or playing audio.&lt;/li>
&lt;li>Ability to &lt;strong>customize the filename for the native process.&lt;/strong> Now it is possible to set the custom name for DotNetBrowser.Chromium.exe and all native process instances will be subsequently renamed.&lt;/li>
&lt;li>&lt;strong>Back-forward navigation history list support.&lt;/strong> Now it is possible to navigate to the particular entry in the back-forward navigation history and even remove some entries from the history.&lt;/li>
&lt;li>&lt;code>Browser.Loading&lt;/code> property which allows to determine whether browser is currently loading something.&lt;/li>
&lt;li>&lt;strong>Editor commands support.&lt;/strong> Editor commands are the commands for text manipulation when editing in a text field, text area or WYSIWYG editor. Also these commands include more common commands like Cut, Copy, Paste, SelectAll, Undo, Redo, which can be executed for the frame in the loaded web page.&lt;/li>
&lt;li>&lt;strong>Web storage API.&lt;/strong> Now it is possible to access local or session web storage and create, store, find and remove key/value pairs in it.&lt;/li>
&lt;li>Ability to &lt;strong>get selected text or HTML for the frame with a specific ID.&lt;/strong>&lt;/li>
&lt;li>Ability to &lt;strong>pause, resume and cancel downloads.&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Password Manager update.&lt;/strong> Now it is possible to be informed about the password update events (when the user enters a new password for the previously saved login).&lt;/li>
&lt;li>&lt;strong>Added RenderGone event.&lt;/strong> This event allows to detect unexpected render process termination and relaunch it by loading the same URL once more.&lt;/li>
&lt;/ul>
&lt;div class="note-block lead">
&lt;p>And the following issues have been fixed in this update:&lt;/p></description></item><item><title>DotNetBrowser 1.8.2</title><link>https://teamdev.com/dotnetbrowser/releases/2016/v1-8-2/</link><pubDate>Tue, 13 Sep 2016 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2016/v1-8-2/</guid><description>&lt;div class="note-block lead">
&lt;p>Preparing the new release, we focused on improvements in these areas:&lt;/p>
&lt;/div>
&lt;h2 id="javascript--net-bridge" data-title>
JavaScript – .NET Bridge&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#javascript--net-bridge
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Implemented C# objects support for JSFunction.Invoke(). In previous versions, only primitive types and DotNetBrowser JS wrappers could be used as parameters. Now it is possible to pass .NET objects as parameters to JavaScript function call.&lt;/li>
&lt;li>Added JavaScript context events. These events can be used to execute any JavaScript code before the web page JavaScript is executed.&lt;/li>
&lt;/ul>
&lt;h2 id="lightweight-rendering-mode" data-title>
Lightweight rendering mode&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#lightweight-rendering-mode
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Simplified embedding for lightweight controls. The previous version allowed embedding lightweight controls from source code only. Now they can be embedded from Toolbox or XAML directly.&lt;/li>
&lt;li>Enhanced performance for saving web page as image in the lightweight mode.&lt;/li>
&lt;li>Improved lightweight rendering performance.&lt;/li>
&lt;/ul>
&lt;h2 id="dom-api" data-title>
DOM API&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#dom-api
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Now you can attach a single event listener to several DOM events by a single call.&lt;/li>
&lt;li>Added LINQ support for XPath. Now you can use LINQ expressions to work with nodes returned after evaluating XPath expression.&lt;/li>
&lt;/ul>
&lt;h2 id="more" data-title>
More&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#more
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>Properties and events of the &lt;code>BrowserView&lt;/code> controls are now available in the Designer.&lt;/li>
&lt;li>Added ability to specify WebRTC IP handling policy. This allows to prevent exposing of the local IP addresses to servers.&lt;/li>
&lt;/ul>
&lt;h2 id="fixes" data-title>
Fixes&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#fixes
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;ul>
&lt;li>DotNetBrowser crash when handling custom cursors. This issue was reproducible when the custom cursor is detected in Chromium, but no image provided for it.&lt;/li>
&lt;li>Several issues in the default context menu implementation.&lt;/li>
&lt;li>ComboBox auto-close issue, which was reproducible when some popup windows were open.&lt;/li>
&lt;li>Issue with debugger hanging on public properties evaluation.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 1.8</title><link>https://teamdev.com/dotnetbrowser/releases/2016/v1-8/</link><pubDate>Mon, 08 Aug 2016 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2016/v1-8/</guid><description>&lt;p>The main change in DotNetBrowser 1.8 is upgrade of its Chromium engine to version 51.0.2704.106.&lt;/p>
&lt;p>In November 2015 Google &lt;a href="https://chrome.googleblog.com/2015/11/updates-to-chrome-platform-support.html"
class="external-link "
target="_blank"
rel="noopener nofollow"
>announced&lt;/a> the end of Chrome/Chromium’s support for Windows XP, as well as Windows Vista, and Mac OS X 10.6, 10.7, and 10.8, since these platforms are no longer actively supported by Microsoft and Apple. Starting with Google Chrome/Chromium 50, these platforms are no longer supported at all. Since DotNetBrowser 1.8 is based on Chromium 51, support of these platforms has been dropped as well.&lt;/p></description></item><item><title>DotNetBrowser 1.7.1</title><link>https://teamdev.com/dotnetbrowser/releases/2016/v1-7-1/</link><pubDate>Mon, 04 Jul 2016 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2016/v1-7-1/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.7.1 comes with the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Update of DOM API. Now it is easier to work with forms fields, modify field values and obtain modified values directly from .NET.&lt;/li>
&lt;li>Improved inter-process communication between .NET and Chromium processes.&lt;/li>
&lt;li>Added spell checker support. Now you can enable or disable spell checking, configure a specific language to use and be notified about spell check completion.&lt;/li>
&lt;li>Added password manager support. Now it is possible to save login credentials or tell Chromium not to save them for a specific website.&lt;/li>
&lt;li>Added media stream device manager API. Now it is possible to choose a non-default web camera or microphone.&lt;/li>
&lt;li>Fixed heavyweight component freezing.&lt;/li>
&lt;li>Fixed keyboard typing latency.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 1.7</title><link>https://teamdev.com/dotnetbrowser/releases/2016/v1-7/</link><pubDate>Tue, 07 Jun 2016 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2016/v1-7/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.7 comes with the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Upgrade to Chromium 49.&lt;/li>
&lt;li>Update of Printing API. Now regular and PDF printing are handled by the same handler.&lt;/li>
&lt;li>Improved JavaScript — C# bridge: now it is possible to access .NET objects and invoke their methods as if they were regular JavaScript objects. Please take a look at the migration guide that we have prepared.&lt;/li>
&lt;li>Improved native process crash handling: now the dumps with information about crash are generated automatically when a process crashes.&lt;/li>
&lt;li>Brand-new Certificate Validation API.&lt;/li>
&lt;li>Intorduced frames IDs hierarchy API. Now it is possible to find the IDs of all the child frames for a specific frame.&lt;/li>
&lt;li>Fix for incorrect rendering on resizing of the lightweight component.&lt;/li>
&lt;/ul>
&lt;p>There were some big changes, too. In this Chromium build support of NPAPI plugins has been removed at all. Now, NPAPI plugins such as Microsoft Silverlight, Java Applets, etc. are not supported. The &lt;code>--enable-npapi&lt;/code> Chromium switcher doesn’t work either. PPAPI plugins such as Adobe Flash work well with this Chromium build.&lt;/p></description></item><item><title>DotNetBrowser 1.6.4</title><link>https://teamdev.com/dotnetbrowser/releases/2016/v1-6-4/</link><pubDate>Wed, 27 Apr 2016 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2016/v1-6-4/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.6.4 contains the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Default context menu implementation.&lt;/li>
&lt;li>PluginInfo support for DotNetBrowser plugins.&lt;/li>
&lt;li>Improved JavaScript C# bridge. Now it is possible to work with JavaScript objects.&lt;/li>
&lt;li>Auto-dispose for browser views, created using the default constructor.&lt;/li>
&lt;li>Fix for incorrect drop-down position and size for lightweight WPF views and non-default screen DPI.&lt;/li>
&lt;li>Fixes for several deadlock issues for heavyweight controls.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 1.6.3</title><link>https://teamdev.com/dotnetbrowser/releases/2016/v1-6-3/</link><pubDate>Tue, 05 Apr 2016 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2016/v1-6-3/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.6.3 contains the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Added print handler for &lt;code>PrintToPDF()&lt;/code> functionality.&lt;/li>
&lt;li>Added &lt;code>InnerText&lt;/code> property support for &lt;code>DOMElement&lt;/code>.&lt;/li>
&lt;li>Implemented &lt;code>GetImage()&lt;/code> for HEAVYWEIGHT mode.&lt;/li>
&lt;li>Implemented mouse and keyboard events for &lt;code>BrowserView&lt;/code>.&lt;/li>
&lt;li>Fixed resizing issue for the default popup implementation.&lt;/li>
&lt;li>Fixed incorrect size calculation for non-default screen DPI.&lt;/li>
&lt;li>Fixed Visibility property for &lt;code>WPFBrowserView&lt;/code>.&lt;/li>
&lt;li>Fixed scrollbar behavior and text selection for LIGHTWEIGHT mode.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 1.6.2</title><link>https://teamdev.com/dotnetbrowser/releases/2016/v1-6-2/</link><pubDate>Thu, 03 Mar 2016 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2016/v1-6-2/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.6.2 contains the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Implemented Text Search API.&lt;/li>
&lt;li>Implemented web cursors support.&lt;/li>
&lt;li>Implemented Flash context menu support.&lt;/li>
&lt;li>Improved Flash Stage3D support. Now DotNetBrowser supports Flash games and applications with real-time interactive 3D graphics.&lt;/li>
&lt;li>Resolved issue with drop-down lists behavior.&lt;/li>
&lt;li>Fixed several native crashes and thread deadlock issues during Browser instantiation/disposal.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 1.6.1</title><link>https://teamdev.com/dotnetbrowser/releases/2016/v1-6-1/</link><pubDate>Wed, 03 Feb 2016 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2016/v1-6-1/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.6.1 contains the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Implemented XPath support.&lt;/li>
&lt;li>Improved Video support (HTML5, Flash, Silverlight): now DotNetBrowser supports access to video-sharing websites, such as Vimeo and Maxdome and also works stably while enabling full screen video mode.&lt;/li>
&lt;li>Resolved issue with NullReferenceException thrown during initialization on Windows 8/8.1/10.&lt;/li>
&lt;li>Improved stability of WinForms/WPF BrowserView control in MS Visual Studio WinForms/XAML UI Designer.&lt;/li>
&lt;li>Fixed thread deadlock issues during Browser instantiation/disposal.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 1.6</title><link>https://teamdev.com/dotnetbrowser/releases/2015/v1-6/</link><pubDate>Tue, 22 Dec 2015 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2015/v1-6/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.6 contains the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Chromium environment variables support has been implemented.&lt;/li>
&lt;li>Support of Remote Debugging URL has been added.&lt;/li>
&lt;li>NetworkDelegate for intercepting all HTTP request/response headers and obtain information about each request/response stage has been added.&lt;/li>
&lt;li>Receiving a list of frames IDs in the currently loaded document has been implemented.&lt;/li>
&lt;li>The issue with NullReferenceException thrown during initialization on Windows 8/8.1/10 has been fixed.&lt;/li>
&lt;li>The issue with TypeInitializationException thrown in VisualStudio 2012 on Windows 10 has been fixed.&lt;/li>
&lt;li>The issue with wrong BrowserView size when DPI is set to 125% has been fixed.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 1.5.2</title><link>https://teamdev.com/dotnetbrowser/releases/2015/v1-5-2/</link><pubDate>Tue, 01 Dec 2015 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2015/v1-5-2/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.5.2 contains the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Cache Storage API has been implemented.&lt;/li>
&lt;li>Environment validation has been disabled.&lt;/li>
&lt;li>The issue when Browser instances share proxy settings has been fixed.&lt;/li>
&lt;li>The issue when proxy authentication doesn&amp;rsquo;t work has been fixed.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 1.5.1</title><link>https://teamdev.com/dotnetbrowser/releases/2015/v1-5-1/</link><pubDate>Wed, 18 Nov 2015 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2015/v1-5-1/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.5.1 contains the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Support of HiDPI monitors on Windows 8/8.1/10 has been implemented.&lt;/li>
&lt;li>The issue with wrong Target attribute in DOMEventListener has been fixed.&lt;/li>
&lt;li>Web page loading time has been improved.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 1.5</title><link>https://teamdev.com/dotnetbrowser/releases/2015/v1-5/</link><pubDate>Mon, 02 Nov 2015 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2015/v1-5/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.5 contains the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Printing API has been implemented. API allows printing web page with different print settings on a printer device or save loaded web page as PDF document.&lt;/li>
&lt;li>Dotted border around focused WPF BrowserView control has been removed.&lt;/li>
&lt;li>Stability has been improved.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 1.4</title><link>https://teamdev.com/dotnetbrowser/releases/2015/v1-4/</link><pubDate>Tue, 27 Oct 2015 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2015/v1-4/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.4 contains the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>GPU-accelerated rendering mode has been implemented.&lt;/li>
&lt;li>Chromium engine has been upgraded to version 43.&lt;/li>
&lt;li>Support of .NET 4.0 has been added.&lt;/li>
&lt;li>Support of Windows Server 2008 and 2012 has been implemented.&lt;/li>
&lt;li>Integration with XAML has been improved.&lt;/li>
&lt;li>The size of DotNetBrowser.Chromium.dll has been decreased (from 74Mb to 43Mb).&lt;/li>
&lt;li>The &lt;code>PluginManager.GetPluginsInfo()&lt;/code> method has been implemented.&lt;/li>
&lt;li>The &lt;code>NetworkService&lt;/code> and &lt;code>NetworkDelegate&lt;/code> classes has been added.&lt;/li>
&lt;li>The &lt;code>NetworkDelegate.OnAuthRequired()&lt;/code> method for handling proxy server, basic, digest, and NTLM authentication has been added.&lt;/li>
&lt;li>Stability and memory usage has been improved.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 1.3</title><link>https://teamdev.com/dotnetbrowser/releases/2015/v1-3/</link><pubDate>Mon, 10 Aug 2015 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2015/v1-3/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.3 contains the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Support of Windows 10 and .NET 4.6 has been implemented.&lt;/li>
&lt;li>Cookies API has been added.&lt;/li>
&lt;li>Custom Context Menu has been added.&lt;/li>
&lt;li>File Downloads API has been implemented.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 1.2.1</title><link>https://teamdev.com/dotnetbrowser/releases/2015/v1-2-1/</link><pubDate>Tue, 07 Jul 2015 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2015/v1-2-1/</guid><description>&lt;h2 id="dom-events-api" data-title>
DOM Events API&lt;span class="nowrap-icon">&amp;nbsp;&lt;a class="anchor-icon" href=#dom-events-api
aria-label="Copy anchor link">&lt;/a>
&lt;/span>&lt;/h2>
&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.2.1 contains the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>DOM Events API has been added.&lt;/li>
&lt;li>Fixed issue when JavaScript .NET Bridge does not work sometimes.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 1.2</title><link>https://teamdev.com/dotnetbrowser/releases/2015/v1-2/</link><pubDate>Fri, 03 Jul 2015 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2015/v1-2/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.2 contains the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>DOM API has been added.&lt;/li>
&lt;li>Zoom API has been added.&lt;/li>
&lt;li>Support of environment with dynamic assembly has been implemented.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 1.1</title><link>https://teamdev.com/dotnetbrowser/releases/2015/v1-1/</link><pubDate>Mon, 08 Jun 2015 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2015/v1-1/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.1 contains the following fixes and improvements.&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Support of Windows 8 and 8.1 has been added.&lt;/li>
&lt;li>Support of Windows Forms has been implemented.&lt;/li>
&lt;li>Automatic extraction of Chromium binaries into user’s temp folder has been implemented. Now you don’t need to configure path to the directory with Chromium binaries, DotNetBrowser will extract them into user’s temp directory and perform all necessary configuration programmatically.&lt;/li>
&lt;/ul></description></item><item><title>DotNetBrowser 1.0</title><link>https://teamdev.com/dotnetbrowser/releases/2015/v1-0/</link><pubDate>Mon, 06 Apr 2015 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2015/v1-0/</guid><description>&lt;p>DotNetBrowser is a .NET Library that allows embedding Chromium-based component into .NET applications to display modern web pages built with HTML5, CSS3, JavaScript, etc.&lt;/p>
&lt;p>DotNetBrowser provides WPF component that you can embed into WPF Desktop Application to display web pages. HTML content is rendered by Chromium engine. The component displays graphics that is rendered by Chromium engine in separate process. The library supports Chromium&amp;rsquo;s Multi-Process Architecture. There are no differences in web page rendering between DotNetBrowser and Google Chrome. The web page will look exactly as in Google Chrome.&lt;/p></description></item><item><title>DotNetBrowser 1.1.1</title><link>https://teamdev.com/dotnetbrowser/releases/2015/v1-1-1/</link><pubDate>Mon, 06 Apr 2015 00:00:00 +0000</pubDate><guid>https://teamdev.com/dotnetbrowser/releases/2015/v1-1-1/</guid><description>&lt;div class="note-block lead">
&lt;p>DotNetBrowser 1.1.1 contains the following features and improvements:&lt;/p>
&lt;/div>
&lt;ul>
&lt;li>Support of both 32-bit and 64-bit architectures has been added.&lt;/li>
&lt;li>JavaScript dialogs for both WinForms and WPF control has been implemented. See &lt;code>DotNetBrowser.WinForms.WinFormsDefaultDialogHandler&lt;/code> and &lt;code>DotNetBrowser.WPF.WPFDefaultDialogHandler&lt;/code> classes.&lt;/li>
&lt;/ul></description></item></channel></rss>