Generally speaking, on a Mac, only text fields are keyboard focusable. If we have to pick a single behavior without a pref, that should be it. Ideally, we should pick up the system-level accessibility prefs and/or an application-level pref.
Unless a user has turned it on, hitting tab and not getting to the next editable text field will cause a WTF exception in most Mac users... --Amanda On Tue, Jan 13, 2009 at 5:44 PM, Ojan Vafai <[email protected]> wrote: > -chromium-reviews, +chromium-dev > Yeah, I buy that. I think the default should be to tab through all focusable > elements. With Safari, it's off by default, which I think means it tabs > through form controls only, not really sure. In either case, I don't think > that matchs web developer expecations very well. > Ojan > > On Tue, Jan 13, 2009 at 2:36 PM, Mike Pinkerton <[email protected]> > wrote: >> >> It should, but probably only if the user has turned it on in the >> accessibility prefs. Otherwise it gets in the way. Safari has some >> extra user prefs for this. >> >> On Tue, Jan 13, 2009 at 4:49 PM, <[email protected]> wrote: >> > LGTM >> > >> > Amanda, Mike, CCing you here to get started a discussion on what >> > tab/option+tab should do in our Mac port. Have you all made a decision >> > as to whether it should iterate though all focusable elements? >> > >> > http://codereview.chromium.org/17399 >> > >> >> >> >> -- >> Mike Pinkerton >> Mac Weenie >> [email protected] > > -- --Amanda --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
