[TIMOB-19100] iOS: New editActions show in reversed order
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2015-07-03T05:38:51.000+0000 |
| Affected Version/s | Release 4.1.0 |
| Fix Version/s | n/a |
| Components | iOS |
| Labels | listview |
| Reporter | Fokke Zandbergen |
| Assignee | Hans Knöchel |
| Created | 2015-06-29T14:39:34.000+0000 |
| Updated | 2017-03-17T18:06:30.000+0000 |
Description
The following example and attached screenshot show that the new
editActions show in the reverse order (LTR).
I would expect the first action in the array to show first (from left) and the last last.
var win = Ti.UI.createWindow();
var listSection = Ti.UI.createListSection({
items: [{
properties: {
canEdit: true,
title: 'Swipe me',
editActions: [{
title: 'First'
}, {
title: 'Second'
}, {
title: 'Third'
}]
}
}]
});
var listView = Ti.UI.createListView({
top: 20,
sections: [listSection]
});
win.add(listView);
win.open();
Attachments
| File | Date | Size |
|---|---|---|
| Screen Shot 2015-06-29 at 16.36.53.png | 2015-06-29T14:38:49.000+0000 | 65345 |
There is a discussion on that topic. The native behaviour is, that the actions are always populated from right to left (reference: http://timbroder.com/2014/08/uitableviewcell-action-swiping-in-ios8-and-swift.html). So i'm not sure whether we should turn this around. Your thoughts?
Well, that's odd but if that's how it works native I guess we close this as invalid.
Closing ticket as invalid.