So far, web kit is working great for me. It looks like safari 3.2 is
still using an older version of the engine, the bug of having to
refresh the page to get it to work is still there. Haven't seen this
at all with web kit.
On Nov 14, 2008, at 7:03 PM, Jacob Schmude wrote:
Hi Esther
Actually ,they do work, but there as been a change in the Webkit
code base. For access keys, you must now press ctrl+option and the
letter. Needless to say this is annoying as all get out, as it
interferes with just about every Voiceover key combination around.
On Nov 14, 2008, at 19:58, Esther wrote:
Hi Mike,
Yes, if you start up WebKit it will look as though Safari is
running, except that things like VO-Shift-M on Web page links will
bring up the contextual menu and other such fixes. You really are
running Safari, but the underlying engine powering it has some
fixes. On the slightly negative side (for me), the access keys for
the Mail Archive site for this list at:
http://www.mail-archive.com/[email protected]/
don't work under WebKit right now, so I can't use Control-I to
shift the list of posts to a set of links indexed by date, and
Control-C to shift the listing back to links ordered by content
into threads. (Or navigate through threads to read the next post
with Control-n and the previous post with Control-p; or use the
analogous commands of Control-f and Control-b to move forwards or
back by date). This went away in September, but the fix will
appear in an upcoming WebKit build. Until then, I fire up Safari
to read and search the Mailing List archives for this list, but use
WebKit for most everything else web-related.
Cheers,
Esther
On Nov 14, 2008, at 2:13 PM, Mike Arrigo wrote:
Hi everyone. I decided to give the latest nightly build of web kit
a try, one thing I noticed, when running the webkit application,
it shows as safari, and even calls itself safari 3.1, is safari
still loading but using the newer web kit engine instead? So far,
it's working really well.
