No, it was a webkit bug. The SA sight didn't refuse to work with
Webkit, certain pages weren't being exposed or rendered properly to
Voiceover. This seems to have been fixed, at least it works properly
for me, in the most recent builds.
On Dec 28, 2008, at 17:08, David Poehlman wrote:
is this not a serotech bug?
----- Original Message -----
From: "Mike Arrigo" <[email protected]>
To: "General discussions on all topics relating to the use of Mac OS
X by
theblind" <[email protected]>
Sent: Sunday, December 28, 2008 4:58 PM
Subject: Re: Opera (was Re: firefox, mozilla and voiceover:)
I have found that using the latest builds of webkit is faster than the
actual safari browser, and several bugs have been fixed. There still
are a couple major bugs with webkit though, one relates to using the s
a mobile network from serotek. If you use the email feature, voice
over is unable to read the email message, the other major bug relates
to voice over just saying button or link sometimes when there may
actually be a label there. I usually use webkit instead of the actual
safari browser though, unless I find a page that is doing something
strange. The other feature that will hopefully be added at some point
is to have on click or mouse over elements announced. If you think
something is clickable, you can select it and it will work, but having
that announced would be good. This will probably require an update to
voice over as well.
On Dec 28, 2008, at 10:55 AM, Jacob Schmude wrote:
Hi there
Opera does still have some glaring Voiceover problems. The biggest
one is that pop-up buttons will not speak at all, so selecting
values in most forms is impossible. there are other minor issues,
but this is the big one. By contrast, multi-select lists usually
work quite well in Opera.
The actual performance of Opera with Voiceover is blazing fast, in
many cases much faster than Safari. To get an idea of how fast Opera
is, visit www.blindcooltech.com with both Safari and Opera. If
that's not a huge page that tests Voiceover's limits in Safari, I
don't know what is--not complex, just ridiculously massive. Safari
takes about twenty seconds to interact with it on my Macbook 2.4ghz.
Opera takes about five seconds. In most normal-sized pages, where
Safari takes several seconds to interact, opera is instantaneous.
The other minor issues include not supporting a lot of navigation
keys--no headings, and the like. It's very much like browsing in
Tiger, though much faster. It also doesn't support Voiceover's
grouped mode, and if you have group mode turned on the page gets
extremely out of order. The Dom in opera seems to order things
differently in any case, so it's probably confusing Voiceover's
grouping function. Voiceover gets a two-dimensional view of the page
in Opera anyway, even without group mode.
All in all, if it weren't for that pop-up button bug, I'd probably
switch to Opera as my main browser. The navigation keys aren't a big
deal for me--they're nice to have, but so many pages don't have good
navigation coded in anyway that I usually forget they're there.
Opera says they're looking into the pop-up button issue, so
hopefully we'll get a fix in the near future.
The major difference between a thing that might go wrong and a
thing that cannot possibly go wrong is that when a thing that cannot
possibly go wrong goes wrong it usually turns out to be impossible to
get at or repair.
--Douglas Adams
