If you have a select in md-dialog, it won't expand or show a scroller so you can't see the values

[treeder]

eg:

[asyncliz]

@e111077 are there any select-specific features like fixed menus or something that would help with this use case?

[e111077]

Workaround for now is to set <md-select menu-fixed> attribute on select. This makes the internal md-menu use position: fixed rather than position: absolute. It's not a perfect solution but works in most cases

This is an issue that is unfortunately going to have to be truly fixed by browser native popover.

[e111077]

@asyncliz testing this out, there seems to be an issue where even with fixed the actions bar is rendered above the menu. It seems that the scroller inside dialog needs a z-index >= 1. Can this change be made? otherwise we'd have to figure out some sort of React portals approach that still works with cascading styles and portaling events

https://lit.dev/playground/#gist=a21cae6b3c4fa1249a1a9e99cb1cf783

[asyncliz]

z-index: 1 on the scroller would be a good fix. It needs a z-index >= 0 to appear on top of the background is all

@treeder would you be able to send a PR?

[e111077]

Sorry, I didn't see the call for a PR, so I have a PR out with tests running internally rn:

#4829

[treeder]

Did your fix make it into 1.0 @e111077 ? Doesn't appear to have.

[Bob1k]

in 1.0 lib version to show over dialog should add menu-positioning="fixed" to md-select

[e111077]

Sorry about the lack of update. Yes, but as @Bob1k said, it uses a new attribute. This is because we eventually have plans to have menu-positioning="top-layer" (or "document" not quite sure on the naming just yet) for the upcoming popover API + anchoring API.

Our friends at Chrome OS (since they only need to support Chrome) are intending to test out menu + popover + anchoring for us.

This should provide a true answer to this problem rather than a workaround