|
|
Rank: Newbie
Groups: Member
Joined: 7/2/2015
Posts: 6
|
Hello,
We are using EO.WebBrowser v3.0.113.0 as a Windows Forms control. The device has a touch screen and runs on Win7 OS.
When we touch on the area within the browser control EO.WebBrowser.WinForm.WebControl, and then touch the area outside of the control (which is a different control in the same form), the outside control never gets the click event. What is a possible solution to that?
Thank you.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi, Please see if your version has this property: http://www.essentialobjects.com/doc/eo.webbrowser.winform.webcontrol.autoprocesscmdkeys.aspxIf you have this property, please try to set it false and see if it helps. If that still does not resolve the issue, please try the latest build from our download page and see if it works. Your version is based on Chrome V33 and the current version is based on V41, which has better touch screen support. Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 7/2/2015
Posts: 6
|
Hello,
We upgraded to the latest EO.WebBrowser v15.1.94.2. We have a parent form with System.Windows.Forms.ContextMenuStrip control that closes menu automatically on focus loss. When we show WebBrowser control while the drop-down application menu is shown, clicking on the WebBrowser control does not hide the menu automatically. Is it "as designed" behavior?
Thanks.
|
|
Rank: Newbie
Groups: Member
Joined: 7/2/2015
Posts: 6
|
Hello,
We have a test project that consists of a windows form containing EO.WebBrowser, ContextMenuStrip, IE WebBrowser and couple of buttons. When ContextMenuStrip is shown, clicking on the form or any other control except EO.WebBrowser will hide the menu. Clicking on EO.WebBrowser does not hide it. Is it possible to verify the behavior? We could submit the test project if you prefer.
Thank you very much.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Thanks for the information. We do not need a test project as we are able to reproduce the problem here. We are still working on this issue though. We will let you know as soon as we have a fix or workaround for you.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi, While we are still working on this on our side, you can use the following temporarly workaround: 1. Handle the WebView's MouseDown event; 2. Inside the WebView's MouseDown event handler, add the following code:
Code: C#
Message m = new Message();
m.Msg = 0x0201;
m.HWnd = webView1.Handle;
Application.FilterMessage(ref m);
This passes a mouse down message to the context menu manager and it will close the context menu for you. Note that you will need to update to the latest build first as WebView.Handle property was only added very recently. Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 7/2/2015
Posts: 6
|
Hello,
The work around did help with the menu.
Now we have a strange problem with a touch interaction. The test app runs on Windows 8 touch enabled platform. We use the latest EO WebBrowser. When using a mouse, everything works fine: we can work with content within the browser control, then click outside of the browser to interact with other controls. If we have new popup browser windows, they get proper focus on mouse click.
The same does not work on touch. If we touch the browser control, the web content within does work properly. But clicking outside of the browser does not release the focus and browser still gets all the events. Same with popup browser windows - we cannot get them to scroll if the main browser control was touched to open them, instead the main browser content scrolls. Looks like touch events are handled differently from mouse events within EO WebBrowser. Is it possible to look into this issue?
Thanks a lot.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi, We have just posted a new build that contains some code adjustments related to touch. We have not been able to reproduce the exact problem you have, so the new build may not fix the issue for you. If that's the case, please try to isolate the problem into a test project and send the test project to us. See here for more instructions: http://www.essentialobjects.com/forum/test_project.aspxAlso this build already contains the Application.FilterMessage workaround. So please remove the workaround code you added earlier. Otherwise FilterMessage will be called twice and may cause additional problems for you. Thanks!
|
|