Skip to content
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

About Routed events bugs #643

Closed
Daoting opened this issue Mar 4, 2019 · 1 comment
Closed

About Routed events bugs #643

Daoting opened this issue Mar 4, 2019 · 1 comment
Labels
kind/bug Something isn't working platform/android 🤖 Categorizes an issue or PR as relevant to the Android platform platform/ios 🍎 Categorizes an issue or PR as relevant to the iOS platform

Comments

@Daoting
Copy link
Contributor

Daoting commented Mar 4, 2019

I'm submitting a...

  • Bug report (I searched for similar issues and did not find one)

Android:

  1. It cannot route to parent element after the child element attached PointerPressed/Tapped/DoubleTapped event, event if Handled=false.

  2. If the parent element AddHandler the PointerPressedEvent, it's child cannot fire PointerPressed event.

  3. If the child element attached Tapped event and set Handled=true, it's parent element cannot receive event even if using AddHandler. DoubleTapped is samed

iOS:

  1. The trigger sequence is different from Android. It's missing an event.
    iOS: Pressed -> Released or Pressed -> Tapped
    Android: Pressed -> Released -> Tapped

Current behavior

Expected behavior

Minimal reproduction of the problem with instructions

Environment

Nuget Package: 

Package Version(s): 

Affected platform(s):
- [x] iOS
- [x] Android
- [ ] WebAssembly
- [ ] Windows
- [ ] Build tasks

Visual Studio
- [ ] 2017 (version: )
- [ ] 2017 Preview (version: )
- [ ] for Mac (version: )

Relevant plugins
- [ ] Resharper (version: )
@jeromelaban jeromelaban added the kind/bug Something isn't working label Mar 6, 2019
@ghuntley ghuntley added platform/android 🤖 Categorizes an issue or PR as relevant to the Android platform platform/ios 🍎 Categorizes an issue or PR as relevant to the iOS platform priority/backlog labels May 22, 2019
@dr1rrb
Copy link
Member

dr1rrb commented Oct 11, 2019

This has been fixed by #1256

I'm closing the issue, feel free to re-open it if there is any issue.

@dr1rrb dr1rrb closed this as completed Oct 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working platform/android 🤖 Categorizes an issue or PR as relevant to the Android platform platform/ios 🍎 Categorizes an issue or PR as relevant to the iOS platform
Projects
None yet
Development

No branches or pull requests

4 participants