Tickets :: Comment on [#919] Ingo Self Defined Header Confusing

* Your Email Address
* Spam protection	Enter the letters below: \ /.___.. .. . . >< _/ \|\/\|\|\ \| \| / \./__.\| \|\| \\|\__\|
Comment	> Two small changes i think would significantly increase Ingo's usability: > > > > 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.
Attachment
Watch this ticket