New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uno.UI regression: Buttons work erratically #2035
Comments
Version 512 correspond to the merge of #1256 which is "kind-of" related to buttons clicks 😜 I'll try to have a look, but in the meantime, do you have anything in the logs? |
Hey @dr1rrb thanks for the quick response! I don't have logs, but maybe @paulovila has more info! |
This is the Chrome Console log I gathered. Please, ignore the "Pressed X" entries. It's a `Console.WriteLine' we added to log when a command executes. |
Actually I don't even get the "Pressed X" 😕 (even if I remove the I can see that the "pointerdown" and "pointerup" events are dispatched to the managed code, and we get back the pointer capture / release sequence ... but nothing happen. |
Ok so I looked a bit deeper, this is due to the (BTW: it means that if you always press the top left corner of buttons, it works properly) |
That's a good start, the area of the button is clickable and the hovering is consistent, but the command is not being triggered |
Hi @paulovila, on my side I don't have any issue with the command not being triggered, at least on WASM. If you have to opportunity to test with this fix #2091 and let me know if it works also for you. |
Hi @dr1rrb thanks, still no joy, I checked out dev/dr/TouchTrans and overwrote Uno.UI package , still the command doesn't get fired |
Hi @paulovila , I just tried:
Are you able to give me more info on how you reproduce it? Note: I also checked that my nuget update was successful by decompiling |
It's working fine , I've tried in Chrome, and Edge, great job! |
Great news, then I close this issue 😀 |
Great work! Thanks! |
Problem
Given a simple calculator app. The calculator buttons do nothing most of times when they're clicked.
Details
There seems to be a regression in Uno.UI, since there's a version in which things work perfectly and a newer version breaks the correct behavior.
Repro steps
I did some research to isolate the regression. This is the table of results I have:
As you can see, the last version that worked is 2.0.324-dev.3171 and the first version that doesn't work is 2.0.512-dev.3446. In the middle, the are some version in which the build is broken (denoated by x).
Affected platform(s):
The text was updated successfully, but these errors were encountered: