![]() If you're having problems with gestures on Spans, we're tracking that issue at #4734.īecause this issue has become so large and contains so many sub-issues unrelated to the original problem, we're asking that anyone who is still experiencing problems with TapGesture on controls to open an issue specific to their situation so that we can address them appropriately. We've also addressed some interaction issues with Frames as parts of DataTemplates, so if you've had a problem with DataTemplates containing Frames not honoring your TapGestures, that's likely been fixed. We've fixed some problems with Frame on Android which may have been preventing TapGesture from firing reliably. If you had problems with TapGestures on Grids, StackLayouts, ContentViews, Borders, Frames, etc., this may have been your actual issue. NET 7 and 8 with layouts on iOS not having user interaction enabled you may have run into these, and now they're fixed. We've also addressed some issues on iOS in. ![]() NET 8, and it's on the consideration list for backporting to. ![]() It's not a gesture issue, it's a ScrollView issue. This issue is an agglomeration of about half a dozen different issues, so I'm going to do my best to address them all.įirst off - if you've seen issues on iOS where some tap gestures on a page fire and others further down do not, and your items are inside of a ScrollView: you might have been hitting a variation of #14257. So maybe u could use this image tap workaround for your case.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |