|Re: Browser control and tab sequencing [message #1232613 is a reply to message #1232267]
||Fri, 17 January 2014 10:25
| Tim Buschtoens
Registered: July 2009
I would guess that this is neither a bug nor a deliberate choice, but
simply default browser behavior. You can try it on a simple HTML page
with an iframe and links in inner and outer frame. If it works there
it's a RAP bug.
If it's not a bug and you have access to the browser widgets content
(same origin policy for frames) you might be able to focus an internal
element using the evalute method. If that works RAP maybe can implement
something like it in the core, otherwise I don't think we can do
anything about it.
Am 16.01.2014 15:50, schrieb John Gymer:
> There does not appear to be any way to use the keyboard to tab into a
> Browser control in RAP. The Browser control itself can take focus, but I
> cannot then go 'into' the page being displayed in the Browser control.
> In SWT this is possible - anything tabbable in the browser control is
> simply made part of the overall tab sequence of the application.
> Is this a bug, or deliberate? If deliberate, why, and is it possible to
> enhance the Browser control in RAP to provide some mechanism for the
> user to use the keyboard to 'get into' the Browser's current page?
> Thanks, John
> p.s. you can probably tell by now that I'm working on 'accessibility' in
> RAP, so there might be a few more like this yet ;)
Professional services for RAP and RCP?
Powered by FUDForum
. Page generated in 0.02563 seconds