I'm not sure if this is a bug exactly, but I had a bit of a confusing issue when upgrading to the latest version in that I had z-index stuff that used different values for the Headroom-enabled element based on whether it had the top class or not, which doesn't seem to be applied anymore on init. In my case, this was an issue because it caused the Headroom element to appear on top of stuff that it shouldn't, but that was fixable by adding a CSS rule to target .headroom:not(.headroom--top):not(.headroom--not-top), i.e. when it's initialized but hasn't decided if it's at the top or not. I figured I'd share that in case someone else runs into this issue.
I'm not sure if this is a bug exactly, but I had a bit of a confusing issue when upgrading to the latest version in that I had
z-index
stuff that used different values for the Headroom-enabled element based on whether it had the top class or not, which doesn't seem to be applied anymore on init. In my case, this was an issue because it caused the Headroom element to appear on top of stuff that it shouldn't, but that was fixable by adding a CSS rule to target.headroom:not(.headroom--top):not(.headroom--not-top)
, i.e. when it's initialized but hasn't decided if it's at the top or not. I figured I'd share that in case someone else runs into this issue.