Hi Rick, Yes, we hear you loud and clear. <grin> Thanks for providing us with this specific testable example. For future reference, please also provide us with the operating system you are running to help us properly document and test reported issues. I just followed the steps you provided in your email and was able to reproduce similar results on my Windows 8.1 PC. There are two issues that I am seeing on this page. The first is that the Adobe Flash plugin crashes when this page loads and Window-Eyes is running. Second, after you perform the Find, Firefox either becomes non-responsive or closes out altogether. In my first two tests, Firefox closed unexpectedly on its own after I performed the Find command. After Firefox closed unexpectedly, Window-Eyes reported that the search string "providers" was not found. After rebooting and testing again, Firefox became unresponsive but didn't close after performing the Find command. In this case, I waited about 30 seconds after losing speech a nd then pressed Control-Alt-W to restart Window-Eyes. Window-Eyes came back up and I was able to close the non-responding Firefox process. These issues did not occur when testing with the other two screen readers I have on my PC. I will be presenting these issues to our engineers and hopefully we will be able to isolate the cause and work on a fix. Once again, thank you for providing this very specific and testable example. This is exactly the type of feedback Ai Squared needs to enhance the stability and performance of Window-Eyes on the web. Kind Regards, Marc -----Original Message----- From: Talk [mailto:[email protected]] On Behalf Of Rick Thomas via Talk Sent: Wednesday, June 24, 2015 6:36 AM To: 'Window-Eyes Discussion List' Subject: W/E Firefox And Lockup
Hi: I just went to a yahoo finance news page, tabbed down quickly to avoid perhaps locking up with the flash plugin message and was able to arrow down and tab in the normal web page a few times. I then did a find to look for the word "providers" and WindowEyes locked up. I tried to fire up narrator but it would not start, it did start after about 30 seconds but still no other keyboard inputs were being recognized. So I couldn't use narrator or fire up jaws to try and fix this WindowEyes problem. When I shut down the computer the last thing I heard was the find window reading before the computer shut down so it was up when WindowEyes locked up the computer. Perhaps if I waited long enough WindowEyes might have come back or narrator would have come back, keyboard input was not getting executed, but I needed the page so just ReBooted. I could not ReStart WindowEyes with the hot keys, remember, no keyboard input, so either waiting and hoping or just ReBooting was my choice at that point and ReBooting has proven faster when this type of WindowEyes lockup happens. Sure hope AI2 has their ears on. 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/msolomon%40aisquared.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
