[TIMOB-11461] Android: Accessibility: After entering the text in the search bar field, it still read aloud the LVH values on Android HoneyComb
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Cannot Reproduce |
Resolution Date | 2012-12-11T23:27:27.000+0000 |
Affected Version/s | Release 3.0.0 |
Fix Version/s | 2012 Sprint 25, 2012 Sprint 25 Core |
Components | Android |
Labels | core, qe-and100112, qe-nfc |
Reporter | Neha Chhabra |
Assignee | Allen Yeung |
Created | 2012-10-13T11:00:30.000+0000 |
Updated | 2013-11-07T18:32:08.000+0000 |
Description
After entering the text in the search bar field, it still read aloud the LVH values on Android HoneyComb.It doesn't not happen on ICS and Jelly Bean.
Steps To Reproduce:
1.Install and launch the Test on device.
2. Click on Second search field and enter the text.
3. Press the back button to hide the soft keyboard.
4. Click again on the second search bar.
Expected Result:
It should not read aloud the LVH values after entering the text.
Actual Result:
It reads aloud the LVH value followed by the entered value after entering the text in the search bar
app.js
var win = Ti.UI.createWindow({
title : 'Welcome',
backgroundColor: "#fff"
});
var search1 = Titanium.UI.createSearchBar({
barColor:'#000',
showCancel:true,
height:43,
top:10,
});
var search2 = Titanium.UI.createSearchBar({
barColor:'#000',
showCancel:true,
height:43,
top:100,
accessibilityLabel: "Search bar2 label.",
accessibilityValue: "Search bar2 value.",
accessibilityHint: "Search bar2 hint"
});
var search3 = Titanium.UI.createSearchBar({
barColor:'#000',
showCancel:true,
height:43,
top:200,
accessibilityHint: "Search bar3 hint",
accessibilityLabel: "Search bar3 label.",
accessibilityValue: "Search bar3 value."
});
var search4 = Titanium.UI.createSearchBar({
barColor:'#000',
showCancel:true,
height:43,
top:300,
accessibilityHidden: true,
accessibilityLabel: "Search bar4 label.",
accessibilityValue: "Search bar4 value.",
accessibilityHint: "Search bar4 hint"
});
win.add(search1);
win.add(search2);
win.add(search3);
win.add(search4);
win.open();
I just tested this, and it reads the LVH values on all versions except for JB. In JB, if there is text inside the text field, it will read that instead. This seems to be a JB feature. I tried the different version of android on a native android app, and I get the same behavior. Could you please retest this again, and verify that it always reads the LVH value, except for JB devices? Also please make sure you have the latest version of talkback installed before testing. If you find any issues please reopen this issue. I'm going to mark this as cannot reproduce for now.
Tested with: SDK:3.1.1.v20130508233955 Appcelerator Studio: 3.1.1.201305072102 OS: OSX 10.7.5 Device: google nexus7(4.1), LG-p970(2.2.2) Cannot reproduce