| Summary | Ingo Self Defined Header Confusing |
| Queue | Ingo |
| Queue Version | 1.0-RC2 |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | Horde Developers (at) |
| Requester | lee (at) disinfo (dot) com |
| Created | 11/30/2004 (7541 days ago) |
| Due | |
| Updated | 12/20/2004 (7521 days ago) |
| Assigned | 12/07/2004 (7534 days ago) |
| Resolved | 12/20/2004 (7521 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Resolved
#1.#2is a UI issue - if you want to test out a newlayout and post screenshots on the ingo list, we will take a look.
State ⇒ Assigned
State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Ingo Self Defined Header Confusing
Queue ⇒ Ingo
1) When adding a filter with self-defined headers, the order of the
fields is currently:
Self Defined Header Select: | Contains Select: | <value> | <header name>
This is very confusing, since the value / header input fields are not
labeled, and one could easily think that since teh drop downs are
ordered "Self Defined Header" then "Contains" that the input fields
should be in the same order (header then value). Anyway a very simple
fix that would make this FAR more intuitive would be to redraw them:
Self Defined Header: | <header name> | Contains: | <value>
This fixes both of the problems above, and make it 100% clear what goes where.
If you want i will create a patch upon request.
2) Many filters inputs require 1200px + screen width when the folders
menu is displayed, otherwise they wrap. When they wrap it looks
terrible, and the input fields lose their implicit meaning. Why not
make each rule input a <li> and then use a <br> after each individual
field select and value input combination? This will solve the wrap
problem and simultaneously make the filter add page look much cleaner.