Hello,

in the changelog you wrote:
Significantly improved Windows Form and WPF input integration (such as shortcuts for menu items) with EO.WebBrowser;

I think that causes a problem in my application.

If I press F10 the webview looses the focus. The MenuStrip gets it.

is it possible to turn the "improvments" off? ;)

best regards

Hi,

F10 is the hotkey for activating the menu. So this is how it supposes to work. As to Shift + F10, I am not sure whether it is a hot key in your application. The rule here is if you use EO.WinForm.WebControl, then it follows Windows Forms application's rule, such as F10 activating MenuStrip or any other hot keys implemented in your application (for example, hot key for a menu item). If you do not want it to work this way, you can use WebView class directly.

Thanks!

This is how it supposes to be. If you use any other standard controls in your application, it will honor the same set of application wide shortcuts. The fact that this did not work in older version does not mean it is the right behavior. In the newer version we brought it one step closer (still not perfect) to have the same behavior as other standard controls, so we do not see any reason to roll this back to the old "wrong" behavior. What we could look into is to give you more option for you to "override" certain keys so that it does not get passed to the application. For example, the multiline textbox would not pass Enter key to the parent form so while usually Enter key would close a dialog but it would not do so if the focus is in a multi-line textbox. So we can look into it to see if there is anyway for you to catch certain keys but there is no guarantee at this point yet before we look into this thoroughly.

can you tell me, how you handle the F10 button?
I tried to prevent the function by using kind of this code ... but F10 does not fire it.

private const int WM_SYSCOMMAND = 0x0112;
private const int SC_KEYMENU = 0xF100;

protected override void WndProc(ref Message m)
{
if (m.Msg == WM_SYSCOMMAND)
{
if (m.WParam.ToInt32() == SC_KEYMENU)
{
m.Result = IntPtr.Zero;
return;
}
}
base.WndProc(ref m);
}

Yes, I understand that you don't provide general Windows support.

But if I don't use EO WebViews in my application F10 and F22 doesn't cause this "Problems".
So I asked what technique you have used. I hope that will help me to find a solution.

... I know that nearly nobody uses F22 ... but without that and F10 my whole application is for trash ...

(please try F22 in your Tabbedbrowser ... Windows 10)

Thank you very much! The first tests looks great,

you saved my weekend ;)