Welcome Guest Search | Active Topics | Sign In | Register

WebBrowser Dev Tools funky after new install Options
Jason
Posted: Friday, February 26, 2016 4:02:39 PM
Rank: Newbie
Groups: Member

Joined: 11/3/2014
Posts: 3
Hi, we just upgraded from WebBrowser 3.0.89.1 to WebBrowser 15.4.1.0 and now our DevTools dialog is acting wacky. Now, if you try to size the dialog by dragging the edge your cursor permanently locks onto the edge of the dialog even after releasing the mouse button. Only after pressing <esc> a few times will it release. Along with this strangeness it also has a problem repainting the dev tools control inside the dialog, so bars of black show up etc. This functionality used to work fine. No code has changed on our end. I have included the code (below) we use to show this functionality. Its WinForms, not WPF. Maybe we need to do something else now that is different than before? I have gone thru the forums and couldn't find anything. We use this functionality out in the field to help us debug issues at customer sites so it is very valuable. Help would be appreciated.

Thanks,
-Jason

Code: C#
internal class EODevTools: IDisposable
	{
		private DevToolsDialog dialog_;
		private static WebView webView_;
		private readonly WebControl webControl_;
		private bool dialogOpen_;

		public static EODevTools GetInstance(WebView webView, WebControl webControl)
		{
			return new EODevTools(webView, webControl);
		}

		private EODevTools(WebView webView, WebControl webControl)
		{
			webView_ = webView;
			webControl_ = webControl;
		}

		public void Dispose()
		{
			if (dialogOpen_)
			{
				dialog_.Close();
			}
		}

		public void ShowDevTools()
		{
			if (!dialogOpen_)
			{
				dialog_ = new DevToolsDialog();
				dialog_.Closed += (sender, args) =>
				{
					webView_.HideDevTools();
					dialogOpen_ = false;
				};
				webView_.ShowDevTools(dialog_.Handle);
				dialog_.Show(webControl_);
				dialogOpen_ = true;
			}
		}
	}

	internal partial class DevToolsDialog : Form
	{
		public DevToolsDialog()
		{
			InitializeComponent();
		}
	}
eo_support
Posted: Friday, February 26, 2016 4:29:29 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,229
Hi,

Your code looks fine. This mostly has to do with the Chrome engine the new version uses since we don't do anything on that part at all. We do have a new version that will be released very soon and it will be based on the latest version of Chrome engine. So I would recommend you to try that version once it's out and then go from there.

Thanks!


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.