Working on something that has a series of vertical drop down menus.
A selection made in the first menu shows a second menu with selections that are children of the parent selection in the first menu
Similarly, selecting an item in the 2nd menu shows a 3rd menu with items that are children of the selection in the 2nd menu and so on.<p>Ultimately, whichever child level you choose to stop at and click submit that would show you filtered search results based on the selections in the parent and child(ren) level(s).<p>However, after a point in time, it can get cumbersome to have to make selections in successive menus if you already know which child menu your selection is in so that you can get to the search results you want quickly.<p>Thinking of implementing a search bar directly in the parent (1st) vertical drop down. The idea is that you could type in this bar and it would reveal all the menu navigation paths that contained the keywords you typed.
You could then simply select the path that applied best and reveal the search results matching that path.<p>I've just never seen something like this implemented elsewhere and was wondering whether that was because it was considered as bad usability or some other reason.<p>Hope that all made sense.<p>Thanks!
Yes and No.<p>I figure its simple enough to code<p><pre><code> select from [input 1] where [input 2] where [input 3]
//I don't actually know SQl so thats likely wrong
</code></pre>
But its a bit sloppy for the user to use.<p>Example:<p>Naughty America's search system (its a porn site, feel free to judge) actually uses this layout (not with drop down menus mind you). But it presents a field of links, its also 3 levels deep.<p>The first field is generic category, second is children of that category, so on and so forth.<p>This system sucks. Its a pain to use and limits how the user can interact with your site. Especially when there is overlap between categories, where a level 2 category might belong to 4-5 different parents, now I have to select each parent category...<p>I swear this was a solved problem when relational databases were invented in the 70's.