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 241828 - Keyboard: Can't move to the Categories field by Tab key.
Keyboard: Can't move to the Categories field by Tab key.
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Contacts
pre-1.5 (obsolete)
Other All
: Normal minor
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks: 242070
 
 
Reported: 2003-04-24 03:29 UTC by Jessie Li
Modified: 2004-09-29 20:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jessie Li 2003-04-24 03:29:06 UTC 
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
Keyboard: Can't move to the Categories field by Tab key.

Steps to reproduce the problem:
1. Start evolution.
2. New a contact.
3. Click Tab, focus move forward until the focus moves to the
Business&Address field.
4. Click Tab again.

Actual Results:
It will move in the field instead of move to the next widget.
You have to use "Shift+Tab" to focus on the Categories descendingly.

Expected Results:
It should focus on the checkbox: This is the mailing address.

How often does this happen? 
always

Additional Information:
Comment 1 Gerardo Marin 2003-04-24 16:37:31 UTC 
Not sure if a tab can be part of address and hence keep focus under a
tab keyboard event.
Minor since you can shift-tab
Comment 2 sheng hao 2004-04-01 07:37:16 UTC 
If the focus on the GtkTextView(the Business&Address field),
follow next steps, you can move the focus to the Categories.
1) Alt+t; (move the focus to the checkbox)
2)  tab ; (move the focus to the Categories widget)

But I don't think it is the best resolvent.
Would you like give me some advice, please?
Comment 3 sheng hao 2004-05-13 08:54:49 UTC 
This bug is no longer in the contact editor in 1.5