Re: Attention: Safari Bug in iOS 10.1 Detected!

2016-10-26 Thread Jim Fettgather
gather > Sent: Wednesday, October 26, 2016 10:38 AM > To: viphone@googlegroups.com > Subject: Re: Attention: Safari Bug in iOS 10.1 Detected! > > This same problem is exhibited when trying to do web searches in Firefox or > the Chrome browser. Also, from what I can tell, even whe

RE: Attention: Safari Bug in iOS 10.1 Detected!

2016-10-26 Thread Sieghard Weitzel
: Wednesday, October 26, 2016 10:38 AM To: viphone@googlegroups.com Subject: Re: Attention: Safari Bug in iOS 10.1 Detected! This same problem is exhibited when trying to do web searches in Firefox or the Chrome browser. Also, from what I can tell, even when searching in the App store, this same

Re: Attention: Safari Bug in iOS 10.1 Detected!

2016-10-26 Thread Jim Fettgather
This same problem is exhibited when trying to do web searches in Firefox or the Chrome browser. Also, from what I can tell, even when searching in the App store, this same inability to review the text that is typed in the search field is there as well. On 10/26/16, Tom Lange

Re: Attention: Safari Bug in iOS 10.1 Detected!

2016-10-26 Thread Tom Lange
Hi Using an iPhone 7 paired with a Braille Sense U2, I can definitely confirm the Safari bug, though I found the same behavior occurred no matter where I went. I tried search fields at amazon.com, bookshare.org and at dogpile.com. In all cases, I'd type something in the search fields and set

Re: Attention: Safari Bug in iOS 10.1 Detected!

2016-10-26 Thread Donna
Hi I can confirm the Safari bug. I want to add that search fields respond differently on different websites. I testing on amazon.com & when flicking through my search term, with the rotor set to characters, the cursor didn't appear to move. When flicking I heard only the word I had typed in

Attention: Safari Bug in iOS 10.1 Detected!

2016-10-26 Thread Gordan Radić
Hi to all! Someone just told me about the Safari bug in recent iOS 10.1 version. I checked it out and here's what I found. Please, try to reproduce it by yourselves and if it is consistent amongst you I believe we should report to Apple Accessibility. I apologise