Material-ui: drop down menu get keyboard focus

[codeuniquely]

When tabbing through a form or page and the tab order shifts onto a Drop Down menu it should get focus and open with the currently selected Index item selected in the menu.

Currently Drop Down Menus don't interact at all when tabbing through controls

[hai-cea]

We'll address this with #51

[hai-cea]

Thanks @codeuniquely - Fixed with SelectField in #846

[tonyxiao]

As of the latest version of Material UI I'm still not getting keyboard focus on the SelectField. When tabbing it skips over the select field and goes straight to the next textfield / button. Is that expected behavior?

[sburgess8]

@hai-cea I am unable to select the DropDownMenu by tabbing through the page. If I don't pass "tabIndex={ 0 }", it skips over the component. With tabIndex, I can't open the dropdown menu with enter, arrows, or spacebar. The :active css selector applies on selection via tab. Tabbing through the items of the dropdown works well once the dropdown is open. This is true for 0.14.4 and 0.15.0-alpha.1 as well.

[wiber]

if one could trigger a click on it when it's onFocus it would look right. haven't found a way to do this.

[wbprice]

I'm also unable to focus SelectField using the keyboard on Material-UI v0.15.0-alpha.1

[NeXTs]

Does anyone has any workaround regarding forcing dropdown respond on tabkey?
It doesn't work for me in 0.15.2

[mikroware]

I am also wondering if there is a workaround. It is pretty annoying when it just skips the SelectField while tabbing through the fields. For [email protected] tabbing does not work.

[micahlisonbee]

+1, it seems this issue has been addressed but not properly fixed in the latest release. I'm on 0.15.3. @hai-cea

[RobRolls]

+1, I'm on 0.15.4 and the SelectField is being skipped when I tab through the UI.

[husterk]

+1, I am using 0.16.0 and I am still not able to select a SelectField component when tabbing through the navigable components on the page. Pressing the Tab key always skips the SelectField components. Please reopen this issue and address it. It is very annoying to our users.