Curious as to what benchmarks you used which found Safari slower than other browsers. Everything I could find shows Safari either the fastest or maybe #2. Maybe there is something wrong. I've heard Safari preferences can get corrupted and bog things down. Booting into recovery and doing a repair permissions usually clears this up.

CB

On 11/10/12 2:34 PM, Shen wrote:
Hi everyone,
I recently decided to take on the task of erasing my hard drive and install a 
clean copy of Mountain Lion. Even though it had been installed over Lion, the 
performance was not bad. But there were just the few little things that made 
enough of a difference to make me wonder. So I decided to install it.
Now that I have been using it for a few weeks, I have noticed a very specific 
behavior with VoiceOver and especially when it comes to Safari.
A couple of weeks ago on this list, people were saying how VoiceOver doesn't 
automatically interact with the HTML content in Safari. I have discovered there 
are 2 causes for this. One reason is that the page has not completely loaded. 
This can happen a lot because Safari is considered one of the slowest browsers. 
For some reason, it takes much longer to load a page than other browsers. If 
VoiceOver detects that it is not 100% done loading the page, it will not 
automatically interact wit the html content.
The other reason has to do with how VoiceOver works with Safari. I have 
discovered that about 50% of the time, VoiceOver will interact with the html 
content automatically when the page is finished loading, and the other 50% of 
the time, it doesn't. The 50% of the time it doesn't, a few things will happen. 
It will not automatically interact with the html content, it will not announce 
the percentage while the page is loading, and if you return to a previous page, 
it will likely not remember the last position.
I also discovered that by toggling VoiceOver off the on, this issue will go 
away. It does get a little annoying that 50% of the time you browse the 
internet, VoiceOver is not behaving as expected and you will need to toggle 
VoiceOver to fix it.
Overall, it's still not bad compare to Lion and Snow Leopard. There was a 
version of Lion that when VoiceOver is not working correctly in Safari, it 
cannot locate any headings. So I feel that it has improved, but still has ways 
to go.


--
¯\_(ツ)_/¯

--
You received this message because you are subscribed to the Google Groups 
"MacVisionaries" group.
To post to this group, send email to macvisionaries@googlegroups.com.
To unsubscribe from this group, send email to 
macvisionaries+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/macvisionaries?hl=en.

Reply via email to