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 677766 - Rotate/Scale/Shear tool dialog: strange TAB key order
Rotate/Scale/Shear tool dialog: strange TAB key order
Status: RESOLVED DUPLICATE of bug 677765
Product: GIMP
Classification: Other
Component: User Interface
2.8.0
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2012-06-09 16:46 UTC by GrafxUser
Modified: 2012-07-28 10:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description GrafxUser 2012-06-09 16:46:14 UTC
How to reproduce:
1. start the Rotate tool
2. click into the 'Angle' field
3. press TAB many times until the 'Angle' field has the focus again.

This should happen:
The focus moves in the visual order of the fields: Angle field -> Angle slider -> Center X field -> Center Y field -> Unit listbox -> Help button -> Reset button -> Rotate button -> Cancel button -> Angle field ...

This actually happens:
The focus moves in the following order: Angle field > Angle slider (not remarkable) -> Center X field -> Center Y field -> Unit listbox -> Unit listbox ...

The Scale tool and Shear tool have a similar strange TAB behavior. The focus doesn't cycle and it's often hard to find out, which widget has the focus.

It happens always
Comment 1 Michael Natterer 2012-06-09 17:46:49 UTC
Works just fine for me, it cycles exactly as it should. Can anyone
reproduce this?
Comment 2 Michael Schumacher 2012-06-11 19:01:11 UTC
Confirming. Works fine for the first try, then fails as described.
Comment 3 Hartmut Kuhse 2012-06-21 17:20:30 UTC
this belongs to Bug 677765
same workaround
Comment 4 GrafxUser 2012-06-21 17:25:14 UTC
Thanks, Hartmut, it works for me!
From a technical point of view this seems to be an issue of proper GUI
initialization.
Comment 5 Michael Natterer 2012-07-28 10:01:35 UTC
Same root problem -> duplicate

*** This bug has been marked as a duplicate of bug 677765 ***