Opened 9 years ago
Closed 5 years ago
#14391 closed defect (patchwelcome)
listening for gestures prevent some other events to be received
Reported by: | cjolif | Owned by: | Evan |
---|---|---|---|
Priority: | high | Milestone: | 1.13 |
Component: | Events | Version: | 1.7.0 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
If I register a tap.doubletap listener on an outer div, I won't anymore receive events on a inner div.
See attached test case.
Attachments (3)
Change History (9)
Changed 9 years ago by
Attachment: | test_block.html added |
---|
comment:1 Changed 9 years ago by
Milestone: | → tbd |
---|
comment:2 Changed 9 years ago by
comment:3 Changed 9 years ago by
This prevents treemap for working. I will have to get rid of dojox/gesture use in treemap if that one is not solved.
Changed 9 years ago by
Attachment: | 14391.patch added |
---|
One possible fix, but still more tests, seems it brings some side effects to swipe
Changed 9 years ago by
Attachment: | test_block_evan.html added |
---|
When running on mobile devices, all touch and gesture events are fired appropriately on the inner node
comment:4 Changed 9 years ago by
Hey Guys,
I had a check, when running on mobile devices, only mouse events are not fired on inner node, all touch and gesture events are fired appropriately, please try the attached test_block_evan.html on mobile.
So I suppose this won't be a problem and break treemap at this moment since you will be using
on(innerNode, touch.release, func(){...})
and it shall work well on either desktop(mapped to ‘onmouseup’) or mobiles(mapped to ’ontouchend‘)?
The fix is still not ideal since in most cases(e.g. swipe), we do need to preventDefault() the native event to have more control for gestures. And this will probably be part of #13048
comment:5 Changed 9 years ago by
Evan, thanks for the hint, using touch.release indeed made it works. Still if you can come up with a fix at some point I think it would worth it.
comment:6 Changed 5 years ago by
Milestone: | tbd → 1.12 |
---|---|
Resolution: | → patchwelcome |
Status: | new → closed |
Given that no one has shown interest in creating a patch in the past 4+ years, I'm closing this as patchwelcome.
I managed to reproduce the problem on both IOS and Android devices. However, it does seem to work fine with mouse input (FF 8 and Chrome 15)