PolymerElements / paper-dropdown-menu

A Material Design browser select element
https://www.webcomponents.org/element/PolymerElements/paper-dropdown-menu
61 stars 107 forks source link

Paper dropdown menus near the bottom of the window should drop up #85

Open dfreedm opened 8 years ago

dfreedm commented 8 years ago

From @CSEMike on October 23, 2015 19:17

Paper dropdowns near the bottom of the window always open down, creating a compressed scroll area that's very difficult to navigate. (This is doubly challenging on OSX, wherein scroll bars are invisible by default.)

A video illustrates this issue in the demo page -- https://drive.google.com/file/d/0B8dway2WcUoSNWZrcFc3LVI0aGM/view?usp=sharing

I'd expect the behavior of polyer dropdowns to match other UI dropdown widgets and drop 'up' rather than down if the dropdown is too close to the bottom of the window and has more room above than below.

Copied from original issue: Polymer/polymer#2616

dfreedm commented 8 years ago

From @miztroh on October 23, 2015 20:23

+1! On Oct 23, 2015 2:17 PM, "Michael Piatek" notifications@github.com wrote:

Paper dropdowns near the bottom of the window always open down, creating a compressed scroll area that's very difficult to navigate. (This is doubly challenging on OSX, wherein scroll bars are invisible by default.)

A video illustrates this issue in the demo page --

https://drive.google.com/file/d/0B8dway2WcUoSNWZrcFc3LVI0aGM/view?usp=sharing

I'd expect the behavior of polyer dropdowns to match other UI dropdown widgets and drop 'up' rather than down if the dropdown is too close to the bottom of the window and has more room above than below.

— Reply to this email directly or view it on GitHub https://github.com/Polymer/polymer/issues/2616.

ozwaldorf commented 8 years ago

Bump. I would love this to be resolved.

ghost commented 8 years ago

+1!

doroginin commented 8 years ago

+1

cdata commented 8 years ago

I think we should add an attribute to paper-dropdown-menu (and iron-dropdown) to enable "automatic" alignment based on the viewport.

militeev commented 8 years ago

+1

sounakpal commented 8 years ago

+1

kornalius commented 8 years ago

+1

cbelden commented 8 years ago

Any update on this issue?

I would be willing to work on a fix, however, I'm not exactly sure where to start. My hunch is that an iron-overlay-behavior method needs to be overridden.

Also, any temp fixes/recommendations would be greatly appreciated. Thanks

Adminiuga commented 5 years ago

Bumping this up. This behavior really annoying.

DrNiels commented 3 years ago

+1