Hi,
I am not sure if there is anything we can do on such issues. Our EO.WebBrowser product provides a .NET "wrapper" for Google's Chromium browser engine so that you can use it in your .NET app. So our focus is on the integration part, not the browser engine itself. As a result, for issues originates in the browser engine, we generally do not investigate since it is not practical for us to investigate or fix browser engine issues.
I would recommend you to try the same page with Google Chrome first and see if you experience the same problem there. And if you do, you can use Google Chrome's built-in developer tools to debug/troubleshoot the problem. Alternatively, you can also use the same debug UI that's built-into our product (inherited from Chromium) to troubleshoot such issues:
https://www.essentialobjects.com/doc/webbrowser/advanced/debug.aspxThanks