keep position fixed for my "div"

Thanks, Sof.

What is happening is that when an element is shifted using CSS3 Transforms, it creates a containing block in which its descendants with fixed position become absolutely positioned.

What I’m working on is an option that will allow you to disable the shifting of the body, so that it won’t be affected when the menu opens. Hoping to have that update out in the next few days ??

Best,

Chris

Hi chris, thanks for your reply and for new update upcoming ?? cool!!

Otherwise, Is that it is possible to make an option (an input field) allowing for example to add all “div” when want to move by “shiftNav-plugin”
??

Best,
Sof.

Hi Sof,

I’m not really sure I follow you. If the content is shifted, the fixed position elements will become absolutely positioned – that’s just how it works with CSS transforms, so the only fix will be to disable that shifting on the entire content area, not just certain elements

I think it’ll be clearer once you see the new setting in the upcoming update ??

Best,

Chris

Hi Chris,

Ok for your reply and I am looking forward to your solution!!! ??

Otherwise is that one can see a “div” with postion: fixed, becoming fixed with verctical position and at the same time an Absolute postion horizontally(cause by pushing -> ShiftNav) ..

Look at this answer: https://stackoverflow.com/questions/5317695/position-fixed-and-absolute-at-the-same-time-how

??

Best,
Sof

Hi Sof,

Version 1.0 was just released ?? Once you update, you can enable the solution by going to Appearance > ShiftNav > General Settings and disabling the “Shift Body” setting. Then only the menu panel will shift, but not the body, so the positioning of your site elements won’t be affected.

The solution you have posted is very content-specific, and wouldn’t be efficient to introduce in a generalized plugin fashion. You could write up custom code to apply to your specific site if that is important to you, but it’s not something that would be handled out of the box with a plugin. That solution is also rather resource intensive as it recalculates on scroll, so it’s not something you’d want to do one more than 1 or 2 elements, and is something you should probably avoid on mobile.

Hope that helps! ??

Chris