haroldkeith / eyes-free

Automatically exported from code.google.com/p/eyes-free
0 stars 0 forks source link

In some menus, TalkBack becomes unresponsive until it reads the whole menu #289

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Bug: When in an app and we open the app's menu and the menu is in a grid style, 
TalkBack reads the whole menu content at once. Not only that, but touching the 
screen to select something doesn't interrupt the reading - only the proximity 
sensor works in this case. Examples of such apps in witch this happens are: OI 
Countdown, RSSDemon, the old (1.x) versions of ES File Explorer, etc. I think 
those apps use the old Android 2.x menu style and that is part of the problem. 
But even so, can't that be fixed? 

What steps will reproduce the problem?
1. Open an app with such menu (with items in a grid). Examples given above. 
TalkBack will start reading the whole menu (all items in it).
2. Try to interrupt TalkBack's reading of the menu by touching somewhere on the 
screen (in the menu). TalkBack will not interrupt its reading of the menu until 
it has finished reading all of its content and it will not read the touched 
object.
3. When TalkBack is still reading the menu content, put your hand over the 
proximity sensor. only then TalkBack interrupts its reading of the menu content.

What is the expected output? What do you see instead?
If we touch an object on the screen, TalkBack should interrupt the reading of 
the menu content and read the newly touched object. But it doesn't.

What version of the product are you using? On what operating system?
I'm using TalkBack 3.4.0 Final on Android 4.1.2 on a Samsung Galaxy Express 
GT-I8730.

Original issue reported on code.google.com by k.kolev1...@gmail.com on 16 Jul 2013 at 11:55