Community
Participate
Working Groups
Initial focus for the browser view is in the URL bar. Tabbing will not bring focus into the browser itself unlike on Windows
Er, by view I meant editor. Sorry.
Steve, is there a know reason why tabbing through children in a Composite would not move focus to the Browser widget as one of the children on MacOS?
'know' should be 'known' :-).
Chrix?
Need to get the focus ring to work on the Browser on the Mac. Dejan - do you want to reassign this to SWT or create a new bug report?
No need for a new bug - moving.
We should try to get help from Apple to get the focus ring work cross Carbon / Cocoa Webkit. On my machine, the carbon webkit examples don't have a working focus ring either (CarbonWeb, SimpleCarbonWeb). On the other hand, the pure Cocoa samples work well (MiniBrowser).
From the comments that Chrix made, this looks like an Apple problem. Is the problem still happening?
Grant, what is the status/target of this bug?
This bug still occurs on 10.4.9 with WebKit 418.9, though it appears to have been addressed in the latest development builds of WebKit. You can test one of these builds by either downloading and building from source (http://webkit.org/building/checkout.html), or by downloading a prebuilt bundle from http://nightly.webkit.org/.
Getting out of the Browser is also broken on Mac OS X 10.5.1: In the ControlExample, Ctrl+Tab does nothing, Ctrl+Shift+Tab sends focus to a singularity.
Grant, did you get a chance to investigate this?
Grant? Is there something we can do here? (Is this NOT_ECLIPSE?)
This is mostly fixed in HEAD, the Browser can now be tabbed into and out of and throughout, so this is no longer an accessibility issue. However there is still a Carbon-specific problem with the native Safari control which can be seen in Safari's CarbonWeb app. If you navigate to a page like http://www.google.com and then repeatedly Shift+Tab until focus leaves the browser area, the focus rectangle moves to the address bar (good) but keys are still delivered to the eclipse.org text field. The Browser saw the same problem, and no workaround could be found other than to disable backward tabbing within Safari-based Browsers (backward-tabbing into a Browser from outside of it works). Closing as NOT_ECLIPSE since I don't think this last issue of backward-tabbing can be addressed.
