Hey @charlie
Thanks for chiming in. Yes you are correct x-bar-fixed
does appear when you have sticky and scroll up both selected. This almost works to not have to duplicate the bar and have the same menu twice in the builder.
The issue is that when the user goes back to the top of the page x-bar-fixed
is still present, and it should IMHO not be present, just like at page load. Optionally add the classes ‘x-bar-pinned’ or ‘x-bar-top’ (although the later is used already and present at all times) when at the top of the page.
Here is my sample at page load:
x-bar x-bar-top x-bar-h x-bar-absolute x-bar-is-sticky e979-e1 mr7-0 mr7-1
vs after scrolling up (and is persistent until page reload):
x-bar x-bar-top x-bar-h x-bar-absolute x-bar-is-sticky e979-e1 mr7-0 mr7-1 x-bar-fixed x-bar-is-visible
Here are a few that Headroom uses not that we have to use all these but would be nice.
"classes" : {
// when element is initialised
"initial" : "headroom",
// when scrolling up
"pinned" : "pinned",
// when scrolling down
"unpinned" : "unpinned",
// when above offset
"top" : "top",
// when below offset
"notTop" : "not-top",
// when at bottom of scroll area
"bottom" : "bottom",
// when not at bottom of scroll area
"notBottom" : "not-bottom",
// when frozen method has been called
"frozen" : "frozen",
// multiple classes are also supported with a space-separated list
// pinned: "headroom--pinned foo bar"
}