The initially focused control in a Java application is not announced when the application comes to the foreground #3753

Closed
nvaccessAuto opened this Issue Jan 8, 2014 · 4 comments

2 participants

@nvaccessAuto

Reported by mdcurran on 2014-01-08 03:55
When a top-level window or frame moves to the foreground, NVDA will read the name and type of the frame, followed by the currently focused control.
However, it seems in Java applications, NVDA is never detecting the initially focused control, therefore not announcing it nor allowing navigation within it.

@nvaccessAuto

Comment 1 by Michael Curran <mick@... on 2014-01-08 07:49
In [402b591]:
```CommitTicketReference repository="" revision="402b591b901f3777e5706cf3415e9bc7d681eafc"
Java Access Bridge support: When a java application comes into the foreground, keep trying to fetch the real focus until a timeout occurs. Iff this fails, fall back to the root java object for the window. Re #3753

@nvaccessAuto

Comment 2 by Michael Curran <mick@... on 2014-01-22 06:23
In [85fe598]:
```CommitTicketReference repository="" revision="85fe5980194a8623d0b6fd32dd6e621fcf8be948"
Merge branch 'javaImprovements' into next. Incubates #3753, #3754, #3755, #3756, #3757, #3770

Changes:
Added labels: incubating
@nvaccessAuto

Comment 3 by Michael Curran <mick@... on 2014-02-07 05:31
In [5bd2574]:
```CommitTicketReference repository="" revision="5bd2574e845f9da8cd4d2452d27b32a5dda79fbb"
Merge branch 'javaImprovements'. Fixes #3753, #3754, #3755, #3756, #3757, #3770

Changes:
Removed labels: incubating
State: closed
@nvaccessAuto

Comment 4 by mdcurran on 2014-02-07 05:36
Changes:
Milestone changed from next to 2014.1

@nvaccessAuto nvaccessAuto added this to the 2014.1 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment