[TIMOB-15547] iOS7: TableViewRow hasChild shows way off compared to iOS6
GitHub Issue | n/a |
Type | Bug |
Priority | Low |
Status | Closed |
Resolution | Won't Do |
Resolution Date | 2019-11-14T19:38:22.000+0000 |
Affected Version/s | Release 3.1.3 |
Fix Version/s | n/a |
Components | iOS |
Labels | SupportTeam |
Reporter | Thomas Neerup |
Assignee | Unknown |
Created | 2013-10-01T09:26:47.000+0000 |
Updated | 2019-11-14T19:38:22.000+0000 |
Description
Problem Description
When adding a Label to a TableViewRow and sets hasChild on IOS7, the label is pushed twice as much to the left as on IOS 6. I know the right/left default on IOS6 is 8 and 15 on IOS7. But when on IOS7 the Label is pushed 2*15 pixels to the left by the hasChild icon on IOS 6 it is only pushed 1*8 pixels
Steps to Reproduce
When adding a Label to a TableViewRow and sets hasChild on IOS7, the label is pushed twice as much to the left as on IOS 6. I know the right/left default on IOS6 is 8 and 15 on IOS7. But when on IOS7 the Label is pushed 2*15 pixels to the left by the hasChild icon on IOS 6 it is only pushed 1*8 pixels
Please see the attached images, or try:
1. Create a new Alloy project.
2. Drop the Attached index.xml to the Views folder
3. Run the project on IOS 7
4. In the Simulator menu select Debug -> Color blended laysers
5. Look at the Right sides of the labelse
6. Do step 3-5 in the IOS 6.1 simulator (edit right to 8 on labels), see the difference
Actual Result
The label is pushed twice on IOS 7
Expected Result
The label should be pushed once like on IOS 6
Attachments
File | Date | Size |
index.xml | 2013-10-01T09:26:48.000+0000 | 1041 |
ios6.png | 2013-10-01T09:26:50.000+0000 | 27046 |
ios7.png | 2013-10-01T09:26:49.000+0000 | 40332 |
Any news on this one? I would be a lot of work to correct this with user code
Closing issue as “Won’t do”. The information, test code, or OS version is currently out of date with our current release (8.2.1.GA as of the date of closure). If community members feel that the issue is still valid, please add a comment, and include code that demonstrates/reproduces the issue.