|
|
Rank: Newbie
Groups: Member
Joined: 12/8/2015
Posts: 2
|
When using touch screen, MouseDown/MouseUp event acts weird (WPF WebControl.WebView). It is fired even when touch is performed outside the WebView.
For example I have WebControl with height 600, however when i click (touch) below my webcontrol, MouseDown event is still fired, even with Y coordinate 900.
When using regular mouse, not a touch screen, everything works correctly.
Is that a bug or am I missing something?
Alternatively, can I somehow cancel that event? The problem is that I am losing the focus in my webView inputs.
Thanks for response.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi, Please try to set this property to "touch-events=disabled" and see if it resolves the issue for you: http://www.essentialobjects.com/doc/eo.webbrowser.runtime.extracommandlineargs.aspxThanks!
|
|
Rank: Newbie
Groups: Member
Joined: 12/8/2015
Posts: 2
|
Hi,
thanks for your response.
Actually, I tried this one meanwhile.
It helped and touch acts correctly.
However, it brings up a new problem.
When I use "touch-events=disabled" , the long-click doesn't work for touch screen. I have to do long-touch and slide to get it work, and that's unfortunately not acceptable.
Do you know how to do it without "touch-events=disabled" or how can I enable long-touch?
Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
In that case it might be a issue in the chrome browser engine and we will wait until we sync with Chrome's codebase first. There are two ways for an application to handle touch events. It can either explicitly declaring that it does support touch events to the OS thus receives touch received events; or if it does not do so, the OS will automatically convert touch events into mouse events and send mouse events to the application instead. Passing "touch-events=disabled" to the browser engine will tell the browser engine to stop declaring that it supports touch event thus completely rely on mouse event. However there will also stop all touch specific events that do not have the equivalent mouse events, such as long touch, pinch zoom, etc.
We do not change any logic by which Chrome handles touch events. So if there is a problem in there, then we will have to wait until we sync with Chrome's codebase next time. We do not forward port individual fixes made in Chrome's main branch because it is not practical for us to do so --- hundreds of changes are being submitted to Chrome's main branch daily. So it will become unmanageable for us very quickly if we were to forward port individual fixes.
Our next update is scheduled early next year. So hopefully once that is done this issue will be resolved.
Thanks!
|
|