Skip to content

md-sidenav-layout child element with fixed position not being fixed #2416

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

Closed
baruchvlz opened this issue Dec 27, 2016 · 3 comments
Closed

md-sidenav-layout child element with fixed position not being fixed #2416

baruchvlz opened this issue Dec 27, 2016 · 3 comments
Assignees

Comments

@baruchvlz
Copy link

baruchvlz commented Dec 27, 2016

Bug, feature request, or proposal:

Bug

What is the expected behavior?

For fixed position element to be fixed

What is the current behavior?

Fixed position element does not get fixed and scrolls up

What are the steps to reproduce?

http://plnkr.co/edit/N9qjtrQTHf13uCWdUPNb?p=preview
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: http://plnkr.co/edit/o077B6uEiiIgkC0S06dd

What is the use-case or motivation for changing an existing behavior?

In my case I'm trying to create a sticky on scroll sub-nav, but it's not working properly.

Which versions of Angular, Material, OS, browsers are affected?

angular-cli: 1.0.0-beta.24
node: 7.2.1
os: darwin x64
@angular/common: 2.3.1
@angular/compiler: 2.3.1
@angular/core: 2.3.1
@angular/forms: 2.3.1
@angular/http: 2.3.1
@angular/material: 2.0.0-beta.1
@angular/platform-browser: 2.3.1
@angular/platform-browser-dynamic: 2.3.1
@angular/router: 3.2.1
@angular/compiler-cli: 2.3.1
@angular/material: 2.0.0-beta.1

Is there anything else we should know?

Possibly related to #1793

Edit
I was trying to tackle this myself and realized it the transform: translate3d(...) that's cause the issue, more here: http://stackoverflow.com/questions/15194313/webkit-css-transform3d-position-fixed-issue

Also my inial search through the issues didn't show #998

@Splaktar
Copy link
Contributor

This is a duplicate of #998

@jelbourn
Copy link
Member

jelbourn commented Jun 6, 2017

See #998

@jelbourn jelbourn closed this as completed Jun 6, 2017
@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 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants