[TIMOB-14799] iOS: Prevent clearing TextField after password field had focus
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Low |
Status | Closed |
Resolution | Won't Fix |
Resolution Date | 2015-09-01T21:55:40.000+0000 |
Affected Version/s | Release 3.1.1, Release 3.2.0 |
Fix Version/s | n/a |
Components | iOS |
Labels | ios, password, textfield |
Reporter | Mindwarp |
Assignee | Hans Knöchel |
Created | 2013-08-09T12:58:52.000+0000 |
Updated | 2017-03-22T23:04:04.000+0000 |
Description
*Problem*
On iOS textfields are cleared by default after some password field had the focus. Is this something that could be prevented. I looked at the docs for textfields, but either I cannot find it or it just isn't there.
*Example code to reproduce*
var win = Ti.UI.createWindow({
backgroundColor : 'white'
});
var tf1 = Ti.UI.createTextField({
value : "textfield1",
passwordMask : true,
top : 10,
width : 200
});
win.add(tf1);
var tf2 = Ti.UI.createTextField({
value : "textfield2",
top : 80,
width: 200
});
win.add(tf2);
win.open();
*Steps to reproduce*
1. click in the password field
2. click in the "normal" textfield
3. press backspace
*Expected result*
The last character of the textfield is deleted
*Actual result*
The entire contents of the textfield is now cleared instead of only the last character.
Tested and confirmed on iOS 6 simulator with Ti SDK 3.1.1 GA and latest 3.2 CI.
Issue Cannot reproduce Titanium Command-Line Interface, CLI version 3.3.0, Titanium SDK version 3.3.0.GA iOS SDK: 7.1 iOS iPhone Simulator: 7.1
[~shameerj] and [~sunila]. We should test this in 3.2.0 and 3.4.0 (latest master). * If it cannot be reproduced in 3.2.0, then mark as Can't Reproduce, with no fix version * If it can be reproduced in 3.2.0 but not in 3.4.0, mark as Fixed in 3.4.0 Reopening.
I see no justification this should have ben re-resolved. See my comments above, follow those instructions, and then report your updated findings.
[~ingo] [~cng]: Checked the issue and created a native project to see the native behaviour and it's the same. Can close this as "Won't fix".
The issue is a native iOS-behaviour and no Ti-related bug. Closing
Closing ticket as "Won't Fix".