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

SideNav with Type Fixed initial resize disappears #579

Closed
mvanrobaeys opened this issue Mar 11, 2017 · 6 comments
Closed

SideNav with Type Fixed initial resize disappears #579

mvanrobaeys opened this issue Mar 11, 2017 · 6 comments

Comments

@mvanrobaeys
Copy link

With 2.0-rc4 I still experience what is described in #552 latest comment.

With large view/windowsize > 992px the SideNav get's pushed out and in at the first window resize. Happens in two steps, Resizing the window one pixel pushes the SideNav out, resizing again brings it back. Happens also when SideNav is visible in medium view and increasing windowsize over 992px. Tested with Edge and Chrome 55.

@ingosch
Copy link

ingosch commented Mar 14, 2017

Fixed SideNav has also an issue when windowsize "jumps" from < 993px to > 992px in a single resize like changing page orientation from portrait to landscape on mobile devices.
If the SideNav is opened it doesn't get shown after flipping the device.
Watch the video to see both bugs. Demo 2.0-rc4 with just SideNav set to FIXED and added padding to the other content.
https://www.youtube.com/watch?v=eaCQnKG0U8o

@kevzlou7979
Copy link
Contributor

Hi @ingosch thanks for the video now i visualize better the issue. Will ping you once i found the solution for this issue.

@BenDol
Copy link
Collaborator

BenDol commented Mar 14, 2017

This appears to be a slight issue with the materialize library, I will look into a fix later today.

@kevzlou7979 kevzlou7979 changed the title fixed Sidenav initial resize disappears SideNav with Type Fixed initial resize disappears Mar 21, 2017
@kevzlou7979
Copy link
Contributor

Fixed via 00ac3e6.

@kevzlou7979
Copy link
Contributor

Just tested this on other projects, it seems that the workaround / solution does not fully solved the issue. Will see other solution soon.

@kevzlou7979
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants