[TIMOB-7963] Ti API: TableViewRow.top, .left, etc. work differently on iOS, Android
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Won't Do |
| Resolution Date | 2020-01-09T21:34:37.000+0000 |
| Affected Version/s | Release 1.7.5 |
| Fix Version/s | n/a |
| Components | TiAPI |
| Labels | parity, tbs-2.1.0 |
| Reporter | Arthur Evans |
| Assignee | Unknown |
| Created | 2011-12-15T13:43:22.000+0000 |
| Updated | 2020-01-09T21:34:37.000+0000 |
Description
On Android, the .top, .left, etc. properties on a tableviewrow affect the layout of the row text (but not the row decorations, such as checkboxes).
On iOS, these properties are ignored.
We should make this behavior more consistent.
This was misfiled as a doc bug; it's a parity bug.
IMHO, iOS behavior should be preferred. Positioning properties (top, left, ...) should have affect on component position within parent container. Row's parent container is TableView(Section) and positioning really doesn't make sense since TableView is a composite component. Text positioning is semantically wrong (although, I am exploiting this to have text padding in a row :) ) and should be replaced with proper property (padding).
It has been decided that this issue should be closed as “Won’t do.” This issue is out of date with our current supported SDK release (7.5.2.GA as of the date of closure), and out of date with mobile OS versions. If community members feel that the issue is still valid, please create a new ticket. Please reference this closed ticket number, include SDK used, comments, and code that demonstrates/reproduces the issue.