Keyboard parity with native browser select

[srikkbhat]

The paper-dropdown-menu works totally different from html select. I am not sure if this is intentional. Some of them seems to be bugs while others are nice to have. I have listed my observations below, would be great if paper-dropdown-menu behaves similar to select.

1. alt+down arrow opens the menu in select. It does not open menu in paper-dropdown
2. In select, once the menu is open, use down arrow to go to desired value and click enter. The menu closes. The menu does not close in paper-dropdown.
3. In select, once the menu is open, use down arrow to go to desired value and click tab. The menu closes after selecting the value and focus moves to next element. In paper-dropdown, pressing tab moves the selection to next item and does not close the menu.
4. In select, once it is focused, pressing a letter rotates the values starting with that letter (without opening the menu). This behavior is unavailable in paper-dropdown.
5. In select, pressing down arrow selects the next value without opening the menu. In paper-dropdown, pressing down arrow opens the menu.

The plunker can be used to quickly compare the features: http://embed.plnkr.co/AhXlpw4FT5fGz00c14Am/preview

[marcelmiguel]

+1

[Silvercast]

+1

[SandeepSuddala]

+1

[wesalvaro]

　６．In select, typing "co" will select "Colorado". In paper-dropdown, it selects "Ohio".

This particular behavior difference is most noticeable to me. Is there another bug tracking it?

[ralexrdz]

maybe forking this effort could help https://github.com/MentallyFriendly/mentallyfriendly-selectbox