Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upHololens click events not working for some people #24698
Comments
|
Might be #24596 - I'll be looking at this this week. |
|
I'm not sure how to reproduce. The UWP port follows these guidelines: https://docs.microsoft.com/en-us/windows/uwp/design/input/handle-pointer-input Mouse down and up are triggered on released and pressed. Click is triggered on tap. What is a "poke"? Is it https://docs.microsoft.com/en-us/uwp/api/windows.ui.xaml.uielement.holding ?
Can you explain a bit more? |
|
By poke I mean that their fingers go through the window instead of briefly making contact. When you click things in servo you hear a sound and a little shadow appears around the clock, that's the shadow ripple I'm talking about. |
|
Would be interesting to see if they miss-click in IE as well. |
|
Just poking in IE doesn't not generate, and poking a link doesn't navigate. So I guess our behavior is consistent with IE at least. |
|
Click events works on Edge, but not on Servo. |
|
Hmm, this should have been fixed in #25076 cc @paulrouget |
|
Back from holidays. I’ll look soon. |
|
This is probably unrelated but I want to point it out just in case it is a part of the problem: clicks as currently implemented in Servo aren't doing a good job of bubbling upward, so for instance if you managed to target the text node inside a button with a click you wouldn't necessarily register a click on the button. #25488 is my attempt to fix that sort of thing. |
Wow, even the mouse move events are not sent. |
|
@paulrouget sorry for the late reply. Click works great at the moment. Thanks! |
I first thought this was a platform issue, but some folks (including @pcwalton) are having trouble clicking links (etc) on Servo's 2D hololens port.
It might be related to #24547 . I haven't really investigated this since I can't easily replicate it myself, but I think these folks poke instead of tap, and that may trigger mouse events instead of touch events or something.
I think the "tap shadow ripple" which happens when you click on servo is still visible for these folks. (Is that
panel.PointerPressed())The DOM synthesizes events at some point and perhaps our events are in conflict with those.
I might let Patrick use the device with some logging at some point.
cc @paulrouget