[TIMOB-9342] MobileWeb: Ensure all UI elements properly disconnect events and nodes on destroy()
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | High |
|---|
| Status | Closed |
|---|
| Resolution | Fixed |
|---|
| Resolution Date | 2012-06-15T15:20:54.000+0000 |
|---|
| Affected Version/s | Release 2.0.1 |
|---|
| Fix Version/s | Release 2.1.0, Sprint 2012-12 MW |
|---|
| Components | MobileWeb |
|---|
| Labels | n/a |
|---|
| Reporter | Chris Barber |
|---|
| Assignee | Chris Barber |
|---|
| Created | 2012-06-01T16:41:51.000+0000 |
|---|
| Updated | 2017-03-03T23:30:10.000+0000 |
|---|
Description
There are a couple of places where not all events, gestures, domnodes are not detached/destroyed when the UI element is explicitly destroyed.
Attachments
| File | Date | Size |
|---|
| app.js | 2012-06-15T15:04:51.000+0000 | 5584 |
Here's all the files that need fixing: * titanium/Ti/_/UI/Element.js * titanium/Ti/UI/ImageView.js * titanium/Ti/UI/Picker.js * titanium/Ti/UI/PickerColumn.js * titanium/Ti/UI/ScrollableView.js * titanium/Ti/UI/TableView.js * titanium/Ti/UI/TextField.js
Pull request: https://github.com/appcelerator/titanium_mobile/pull/2412
Test with attached app.js and KitchenSink.
Closing ticket as MobileWeb is no longer supported.