| Summary | Basic Seach form behaves unintuitively |
| Queue | Turba |
| Queue Version | 2.1.3 |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | chuck (at) horde (dot) org |
| Requester | Otto.Stolz (at) uni-konstanz (dot) de |
| Created | 1/18/07 (7100 days ago) |
| Due | |
| Updated | 1/22/07 (7096 days ago) |
| Assigned | 1/20/07 (7098 days ago) |
| Resolved | 1/22/07 (7096 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
Assigned to Chuck Hagenbuch
State ⇒ Feedback
the wording still works for me. If people agree it can be merged to
FW_3.
State ⇒
simpler == better.
State ⇒ Feedback
Priority ⇒ 1. Low
State ⇒ Unconfirmed
Queue ⇒ Turba
Summary ⇒ Basic Seach form behaves unintuively
Type ⇒ Bug
Find (the search field), Matching (the search argument), From (the
address book to be searched), and Search (the submit button). A user
will normally fill in these fields from left to right, ending with the
Search button.
Now, if the user selects, in the From field, an address book, the
selection in the Find field is reverted to its default. This may well
go unnoticed, so the user will eventually miss the desired result.
Two possible solutions:
- put the From field to the left,
- or keep the selection from the Find field, if the newly selected
address book has a search field named as the previously selected one.