md-autocomplete + scroll

[0101adm]

0.11.4

result box does not stick to element when window is scrolled.

[Splaktar]

Also visible here on HEAD.

[EladBezalel]

It may be a feature 😅:
On google sheets if you edit a cell and scroll down the edit is still available but it's mentioned there what cell you're editing and it's highlighted

[flipvh]

We have started using angular material because it has some sweet components. Unfortunately there are some issues with overall behaviours, such as the one here. Since I think it is very difficult to solve all this consistently, on short term, and with a high level of success for all different ways you can build your (css) layout, a suggestion:

Why not provide us with some classes on the html or body element during an interaction with for example autocomplete suggestions instead of just adding css directly to the dom? This way we can at least solve most of these behaviour issues for our own situation? Until there is a great way to do it consistently within Material design layout.

Given that many people want to use angular-material components, I think it could be a great strategy to make it more easy to start without restricting them to use a rather opinionated way to build your higher level css layout/choices.