It is totally non-intuitive that you can only search on one field at a time. If that's the case, a better design would be a drop down to select the search field, then a text box to enter the search criteria. The current design gives the impression that you can search on any and all of the fields you want.

The way it should work is the user should be able to fill in any field they want to search on. There should be one button on the form that then launches the search. If the user enters data for two fields, both are searched, three fields would search that way, etc.



>I will have this one adjusted by the end of the day. If you spot more locations like this, you may let me know.
>
>>Another place is when doing a member search. It isn't intuitive that I have to click into each of the search fields and that pressing Enter will start the search. A "Search" button on the form would make more sense.
>
>All the lists support only one field for the search at a time. Because, lists have multiple columns, we do not include a search icon on every column. Otherwise, this would enlarge the list and columns and would create empty areas. Also, as lists are pretty much everywhere, this has become a standard.
>
>I still have a note on that one however. It is possible that it will be adjusted to be a one search option on top of it, acting as a general search. We would still have to support two modes on that one however as many want to search by columns on the members area. But, the universal search is quite nice. We see that one wherever there is the ShowHeader class, which is the class used to drive all those lists from the main page, such as Class & method, News, Links, etc.