Hopefully the webkit developers can be made aware that control option can't be used for access keys due to it being used for VO,
On Nov 19, 2008, at 8:20 PM, Jacob Schmude wrote:

Well, a simple platform check could work around that. Apparently they do plan to do this, so that if it's on Mac it's just the ctrl key like it used to be. As far as I know they haven't done it yet though. I know exactly where it came from, as even when Webkit exposes the access keys to VO it calls the option key the alt key. It's kind of funny to here voice over say "search, ctrl+alt+f." Still, I'm not sure how this one got passed the webkit accessibility folks. Ah well.



On Nov 19, 2008, at 14:17, Chris Blouch wrote:

This is probably a holdover from Windows where nearly every key combination is used by either the OS, browser or AT like Jaws except the control+alt set.

CB

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.










Reply via email to