I’m trying Safari again as my default browser. So far my complaints are the same as they were last time I used it:
- Limited support for the Title attribute.
- Cannot tab to checkboxes and buttons.
- No Accesskey support.
- No type-ahead find.
Camino isn’t perfect either. Type-ahead-find support is only half-implemented. It doesn’t have Accesskey support or the tabbing to checkboxes and buttons (I could swear it used to), but it still feels a bit more polished than Safari. Also, Safari is still a bit
Alex, in the work that we are doing for Airframe, we just recently created a partnership with Apple in regards to getting the product to work in Safari. They are very responsive and helpful in fixing or resolving any issues like the ones you have above! Some of the things you mentioned are going to end up being the same issues we will have i.e. AccessKey support. I’ll let you know how it goes, and whether or not we have any impact on it.
These are all issues that have been reported MANY times to Apple. I’ve reported them myself with the bug button and I read them being lamented constantly on Surfin Safari (before comments were closed). I’m sure at least some of them will be addressed in the next release – whenever that is.
All controls on a website are treated the same way as operating system controls — in other words, tabbing between text fields only is the default.
I can’t fully explain the location of this in your system preferences, as mine are likely different (I’m on Panther 7B21), but in your keyboard preferences turn on “full keyboard access”. This will then enable tabbing to all controls.
I’ve heard this before, and I have that enabled (it is in the Keyboard preference pane) but I don’t see it working… I’m on 10.2.6.
It may be time to move over to Safari full time now. Version 1.2 adds accesskey support and with SAFT providing the type-ahead find functionality, it is definitely catching up with Camino.
Not everything is perfect just yet though:
SAFT needs …