(sidenav) elements with `position: fixed` inside `md-sidenav-layout`

[fxck]

Because of transform: translate3d(0, 0, 0) on md-sidenav-layout any element with position: fixed inside it will act as if it had position: absolute or static instead. It's an expected behaviour, but it's annoying nevertheless.

Could we either remove that transform from md-sidenav-layout(it's only there because of performance I suppose), or add more examples to Portal and mention it as a workaround in docs, since portal could probably solve this by basically putting the element that needs to be fixed next to the md-sidenav-layout in the dom tree.

cc @hansl @jelbourn

[fxck]

https://gist.github.com/fxck/b668f7fec77d7b28d8c7ce6b706601f7

here's a component that takes whatever is inside it and puts it to the body using material2 overlay

[fxck]

@jelbourn this is still a thing, can you label it please?

[jelbourn]

We need to discuss whether we consider this a bug or not.

[cortopy]

In my opinion this is a bug insofar as it is the equivalent of putting a ban on fixed elements. I am now trying to create a fab button on the bottom right corner of the screen. Because of this issue I'm unable to do so unless I use solution provided by @fxck

[bergben]

Is the workaround from @fxck still working?
I am getting EXCEPTION: Must provide a portal to attach...

[mmalerba]

I recommend just absolutely positioning the fab outside the scrollable region: http://plnkr.co/edit/VItn3Y2AaTzpzIykTTyH?p=preview

[cortopy]

that's clever @mmalerba but it wouldn't work in my case. My button is inside a router outlet as the fab is not always needed. Your solution would work great for cases where fixed elements should be visible in every view though.

Also, it would mean a lot of boilerplate to pass events to other components within the scrollable area