After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 440496 - [blocked] shift-tab does not work with JDK 1.6 and JABW 1.18
[blocked] shift-tab does not work with JDK 1.6 and JABW 1.18
Status: RESOLVED NOTGNOME
Product: orca
Classification: Applications
Component: general
2.17.x
Other Linux
: Normal normal
: ---
Assigned To: Willie Walker
Orca Maintainers
Depends on: 440783
Blocks: orca-java
 
 
Reported: 2007-05-22 16:27 UTC by Lynn Monsanto
Modified: 2007-12-11 18:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Lynn Monsanto 2007-05-22 16:27:29 UTC 
There is a regression from JDK 1.5 where typing shift-tab does not move keyboard focus to the previous component in the tab traversal cycle. 

1. Shift-tab works on JDK 1.5 with and without the Java Access Bridge 1.18 (JABG) running.

2. Shift-tab works on JDK 1.6 without the JABG running.

3. Shift-tab does not work on JDK 1.6 with the JABG running.

I haven't tested with previous versions since I can't get JABG versions earlier than 1.18 to build on my machine (GNOME 2.18.1)
Comment 1 Willie Walker 2007-05-22 16:40:06 UTC 
Is this restricted to magnification?
Comment 2 Lynn Monsanto 2007-05-22 16:44:48 UTC 
No, I hit the wrong list item.
Comment 3 Willie Walker 2007-05-22 21:39:57 UTC 
This is really bad.  Please file a bug against the JABG and then mark this one as blocked?
Comment 4 Willie Walker 2007-05-22 21:40:36 UTC 
Sorry - reverting back to normal/normal since one can revert back to JDK 1.5 as a workaround.
Comment 5 Lynn Monsanto 2007-05-23 18:19:06 UTC 
I'm reassigning this bug to the Java Access Bridge for GNOME and marking this bug as BLOCKED.
Comment 6 Willie Walker 2007-05-25 16:27:32 UTC 
Removing target milestone from [blocked] bugs.  We have little control over them, so we're better off letting priority and severity be our guide for poking the related components.
Comment 7 Willie Walker 2007-12-11 18:55:10 UTC 
This appears to be fixed in the latest Java platform I have:

java version "1.6.0_04"
Java(TM) SE Runtime Environment (build 1.6.0_04-b10)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)