Weird startAt behavior?

[PhyxionNL]

I'm not entirely sure what startAt is doing
"Stick the menu at XXXpx from the top of the this() (nav container)"

I expected that this would start the sticky element at XXXpx from the top, but setting this means that the element you want to stick is scrolled over for the first XXXpx until it actually works. So, I changed a few things to get what I want:

            /* 1.) As soon as we start scrolling */
            if (windowPosition >= $selfScrollTop - options.startAt) {

            /* 3.) As soon as we get back to the top of the page */
            /* If top of the window is over this() (nav container) */
            if (windowPosition + options.startAt <= $selfScrollTop) {

Now, I don't know what the expected behavior is but if the current implementation is correct, can we get something like this added?

[jbutko]

My original intention was exactly as you described here: ""..but setting this means that the element you want to stick is scrolled over for the first XXXpx until it actually works."

If I understand well your desired intention is to have offset from window top - try set navOffset option and let me know if it is what you were looking for.

Will leave it as it is now.

[PhyxionNL]

navOffset is indeed an offset but not what I am looking for. Let's say this:

• I want my element 50px from top.
• With navOffset the element is first at completely at the top of the page (0px) and is then wrapped 50px from the top.

However, it looks much better when the element never gets to the top but starts with the fixed position when its already at 50px from top (so it doesn't just flick to the navOffset). I would appreciate it if you add another setting to this, or better: use the current properties (also use navOffset from the top, if a user wants the current behavior again they can add the XXX pixels to startAt and it'll be the same again).

[jbutko]

I understand what's on your mind. I tried to implement this but with no expected result. I therefore removed navOffset option completely due to unstable behaviour. Maybe in the future I will play with this a bit again. Anyway fell free to submit a pull request if you find any working solution by yourself.

[PhyxionNL]

The code I posted (pastebin) in the other thread had the expected behavior. Shouldn't be too hard to replace what I used now (options.startAt) with the navOffset I think.

[jbutko]

Try it now but still not working as you wish. It also breaks active class highlighting so this need to be adjusted as well.
If you want to contribute with this feel free to fork the repo and submit pull request. Thanks anyway.

[PhyxionNL]

I will check it out soon. The version I posted on pastebin is what we have live now, it is working as expected with regards to what I describe above. I'll see if I can integrate this again somehow that it's working.