Unexpected behavior

If DotNetBrowser behaves unexpectedly, try reproducing the same behavior in Chromium and see if it persists. Very often the behavior is expected, and this is just how the library works.

  • Chromium 102 x64 and x86 (DotNetBrowser 2.15 and higher)
  • Chromium 100 x64 and x86 (DotNetBrowser 2.13 — 2.14)
  • Chromium 98 x64 and x86 (DotNetBrowser 2.12)
  • Chromium 96 x64 and x86 (DotNetBrowser 2.11)
  • Chromium 94 x64 and x86 (DotNetBrowser 2.10)
  • Chromium 92 x64 and x86 (DotNetBrowser 2.9)
  • Chromium 91 x64 and x86 (DotNetBrowser 2.7 — 2.8)
  • Chromium 90 x64 and x86 (DotNetBrowser 2.6)
  • Chromium 88 x64 and x86 (DotNetBrowser 2.5)
  • Chromium 84 x64 and x86 (DotNetBrowser 2.3 — 2.4)
  • Chromium 79 x64 and x86 (DotNetBrowser 2.1 — 2.2)
  • Chromium 69 x64 and x86 (DotNetBrowser 1.20 — 2.0)

If you see that the same functionality works differently in Chromium and DotNetBrowser, submit a ticket with the details of the issue, the environment in question, and steps to reproduce it.

Go Top