Closed pawelblaszczyk5 closed 1 year ago
Android 10, chrome as well
@pawelblaszczyk5 you've found the specific combination of hardware, os and browser that break the thing π .
I'll try to tackle it tomorrow βΊοΈ
Okay, so I played with it a bit and it seems to be related to to detecting presses from my mobile device as a "virtual".
Here in the menu sub-trigger there is a check whether it's a "touch" "pointerType" and the sub-menu is opened only in that case. As I mentioned before, my device is detected as a "virtual" however π So I tried to check, why it's treated like that.
The pointerDown events on my device are somehow triggered with "width" and "height" set to "0". I know it's a code ported from React Aria and it seems that unfortunately this isn't a reliable way of detecting whether a pointer event is virtual.
fixed in v0.6.0
since we do not use onPress
anymore.
Describe the bug Nested context/dropdown menu can't be opened. Clicking on the trigger properly focuses it but the submenu isn't opened.
To Reproduce Steps to reproduce the behavior:
Expected behavior Sub menu should be probably opened
Screenshots
https://user-images.githubusercontent.com/54995479/213496363-58b2d0af-c7bf-441d-a176-d9549cf900b4.mp4
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
Additional context
I tried to debug the problem with mobile inspector. There aren't any errors and the submenu error is properly triggered. What's interesting is the fact that when I triggered clicks from inspector emulator it worked on phone. Maybe some issue with virtual pointer and press primitive? π€
I was testing it a bit there. Clicks from my mobile device are detected as "virtual" via usePress primitive and they behave a bit strangely. Basically after I tap the button no event is triggered, and after releasing it all "press start with virtual", "press end with virtual" and "press with virtual" show up.