GitHub Issue | n/a |
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Invalid |
Resolution Date | 2017-07-10T21:46:35.000+0000 |
Affected Version/s | Release 1.8.0.1, Release 2.0.0 |
Fix Version/s | n/a |
Components | Android |
Labels | api, parity, qe-and11612, qe-ios11612 |
Reporter | Dustin Hyde |
Assignee | Ingo Muschenetz |
Created | 2012-01-16T18:29:48.000+0000 |
Updated | 2017-07-10T21:46:42.000+0000 |
Android and iOS have different and sometimes non-functional UI event listener support.
Using the attached EventTest with the "singletap" event and Ti.UI.Window and Ti.UI.Button UI components,
an accurate behavior matrix is included below as an example, but the overall behavior is similar between all events and UI elements.
Results:
Event Used (for both UI components): singletap
UI Component 1 (used to fire the event): Window
Runtime - Result:
Android V8 - can't re-add event listener
Android Rhino - can't remove event listener
iOS 5.0 - can add and remove event listener (correct behavior)
UI Component 2 (used to fire the event): Button
Runtime - Result:
Android V8 - can add and remove event listener (correct behavior)
Android Rhino - can add and remove event listener (correct behavior)
iOS 5.0 - can't add event listener
Steps to Reproduce:
1. Run attached EventTest project using code-specified (at the top of the file) event and UI component.
2. Observe results.
I'm looking into the iOS version, but should we split this ticket into two sub-tickets, one for Android's issues, one for iOS's issues?
Could not reproduce the iOS add inability issue. Was this fixed by TIMOB-7540?
@Blain - I would prefer to mark this ticket as Ti API ticket instead of creating different tickets.
Can not reproduce on Android.
@Ping - you need to compare iOS and Android behavior side by side for all the scenarios described in this ticket before resolving it.
Closing ticket due to time passed and lack of progress for a number of years. Please open a new ticket if there are any problems.