Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

md-sidenav-layout should not prevent use of position:fixed #778

Closed
Hades32 opened this issue Jun 28, 2016 · 5 comments · Fixed by #6712
Closed

md-sidenav-layout should not prevent use of position:fixed #778

Hades32 opened this issue Jun 28, 2016 · 5 comments · Fixed by #6712
Assignees
Labels
needs: discussion Further discussion with the team is needed before proceeding

Comments

@Hades32
Copy link

Hades32 commented Jun 28, 2016

package version: Alpha5.2

md-sidenav-layout seems to work with with css transforms what in turn breaks position:fixed as this establishes a new viewport.

This makes it impossible to place floating elements inside content in this layout.

I use the content as my router-outlet (what probably many will do). In my content I want to use a floating md-fab button which I now have to place in the main application component. this sucks.

@AmirTugi
Copy link

AmirTugi commented Oct 7, 2016

+1 Experiencing it right now

@sebastianhaas
Copy link

Confirm that this is still an issue. It's really really annoying. Even if I manage to put it outside the sidenav-layout (which is not so easy to achieve since I have to pass icon, click handler/router link etc.), the fab isn't affected by the black transparent overlay on sidenav.open() anymore which is a big visual break.

@petrosalema
Copy link

See also 👉🏾 #998

@safaahammoud
Copy link

Adding z-index 1000 to the parent which has position fixed would fix the issue.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 14, 2019
@mmalerba mmalerba added the needs: discussion Further discussion with the team is needed before proceeding label Mar 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs: discussion Further discussion with the team is needed before proceeding
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants