[TIMOB-3611] iOS: TableViewRow backgroundGradient disappears when clicked and held
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Won't Do |
| Resolution Date | 2020-01-09T19:02:29.000+0000 |
| Affected Version/s | Release 2.0.1, Release 3.1.0, Release 3.2.0 |
| Fix Version/s | n/a |
| Components | iOS |
| Labels | reprod, supportTeam |
| Reporter | Pedro Enrique |
| Assignee | Eric Merriman |
| Created | 2011-04-18T12:29:23.000+0000 |
| Updated | 2020-01-09T19:02:29.000+0000 |
Description
The selectionStyle property of the tableViewRow is set to 'none' so that the row remains static in response to user touch.
However, when clicked and hold on the row the background gradient disappears. A quick click does not trigger the behavior.
var win = Ti.UI.createWindow();
var table = Ti.UI.createTableView();
var row = Ti.UI.createTableViewRow({
backgroundColor: '#F00',
backgroundGradient: {
type:'linear',
colors:['#FFF','#000'],
startPoint:{x:0,y:'0%'},
endPoint:{x:0,y:'100%'}
},
selectionStyle: 'none',
height: 100
});
table.appendRow(row);
win.add(table);
win.open();
Bug is still valid, occurs in: TiMOB: 1.8.0.v20111028154620 Studio: 1.0.6.201110251616 OS: Mac OS X Lion Devices tested on: iPhone 5.0, iPod 4.3.5, iPad 4.3.5 Note: When gradient disappeared, it was replaced by solid red. Gradient re-appeared on touch exit.
Issue still exists.
It works fine when comment out the line colors:['#FFF','#000'], and it seems that its expected behavior.
I have been able to reproduce this issue with the following environment; iPhone 7 (10.2) MacOS 10.11.6 (15G31) Studio 4.9.0.201705302345 Ti SDK 6.1.1.v20170609091155 Appc NPM 4.2.9 Appc CLI 6.2.1 Ti CLI 5.0.13 Alloy 1.9.11 Arrow 2.0.0 Xcode 8.2 (8C38) Node v4.8.2 Java 1.8.0_131
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. Updating, or creating code may not reproduce the issue reported, or be a valid test case. 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.