Hello I'm experiencing the same thing Katie Lady Sent from my iPhone
> On Aug 19, 2015, at 1:24 PM, Rick Thomas via Talk > <[email protected]> wrote: > > Hi: Today WE has decided to lock up in my Amazon attempts to navigate > between prime movies and tv ahows and in some desktop apps. > It seems in Internet Explorer that we gets stuck in some of the search > objects defined on the page as far as I can tell. > In my own desktop app it seems to just dying in the middle of a read to end > or even while arrowing up and down in a standard text box and requires a > reboot since a restart what, insert alt or control alt w doesn't seem to do > anything accept play the chime and let me know we has restarted but doesn't > fix anything. > In IE it seems to be worst, narrator with WE will read some things where WE > is completely silent with WE alone and JAWs seems to work completely > properly with the page so it is not something to do with the page itself. > In fact, on one page where we died I could use the ctl-shift-w and the page > read but the up and down arrows nor the tab did anything, WE was as dead as > a 100 year old fruit fly. > Note that using jaws or narrator that we seems to be in some search box or > area of the page if that helps. > WE has not exhibited this behavior in the past so I am wondering what is > going on. I have not, to my knowledge updated WE nor anything else so this > is a new bug in Windoweyes I guess. > I don't like to use the word garbage but I am beginning to wonder how long > these types of problems can occur before that word becomes viable as a word > to describe a piece of software without fixes being implemented in updates. > By the way, anotherr situation is that, just like I tried to do reviewing > this message, WE will not review any text using the alt-ctl-r command, read > to end. > So I have to go through it, like the pages in other text objects like > NotePad and perhaps some websites, manually one line at a time so WE is not > working here either. > OK, so it wouldn't read using read to end for several trys. I fixed a > spelling error, obvious by listening to the text, and now WE will read to > end this message??? > Anyway, have you noticed this behavior and do you think WE has updated > itself with some invalid, buggy version or do you think one of the scripts > is bad or not being loaded or what do you think might > I also am having some troubles ith locating line beginnings in text > documents bu t that is a minor problem, just seems WE is not very stable at > all today. > be going on here?Rick USA > > > _______________________________________________ > Any views or opinions presented in this email are solely those of the author > and do not necessarily represent those of Ai Squared. > > For membership options, visit > http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/ktpurity%40gmail.com. > For subscription options, visit > http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com > List archives can be found at > http://lists.window-eyes.com/private.cgi/talk-window-eyes.com _______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
