Bad practice for dropdowns to cover buttons?
I have a text field that shows matches in a dropdown when the user starts typing. Below the field are buttons. When the dropdown is activated it covers the buttons. However the dropdown will go away before the user will need to select the buttons, because the user will either a) select the desired match from the dropdown, or b) type their own text that doesn't match anything in the dropdown -- in which case the dropdown goes away.
Is it bad practice to have a dropdown that covers other components? Would it be better to have the dropdown above the field instead, so as not to cover the buttons?
Marcee last edited by
To me, any element that when interacting covers another is a bad practice if it's not its specific function. Especially on the screen where there's more than enough space and resources.
For the example in the question: accordions.