Pressing key Home or End breaks Affix positioning

[gustavohban]

You can check this right on the Bootstrap website.
I was able to replicate this issue using Chrome and IE 11.
Firefox worked fine.

How to reproduce:

Using end key:

1 - Navigate to http://getbootstrap.com/css/
2 - Without scrolling, press the keyboard key ''end"

** The affix element is supposed to go through .affix-top to .affix-bottom, but instead the final class is .affix

Using home key:

1 - Navigate to http://getbootstrap.com/css/
2 - Scroll down the page until you reach the bottom/footer
3 - At the bottom, press the key "home"

** Is the same problem, but now the affix element is supposed to go trough .affix-bottom to .affix-top, but again the final class is .affix

[cvrebert]

Duplicate of #9609.

[kkirsche]

Is it due to performance that the Affix plugin doesn't use @fat's snippet or something similar watching for a home / end key press or is there another reason?

[cvrebert]

I'm guessing he considered the missing scroll event to be a browser bug.
The thing is, at least on OS X, current Chrome does fire a scroll event when pressing the equivalent of Home/End, yet the Affix positioning bug still occurs.

[cvrebert]

Seems to me like there's a bug in the Affix.prototype.getState() logic.
When in the bottom state, top can never be returned as the new state, although that's exactly what seems to be needed here.
If you're at the bottom of the page, this.affixed is bottom and getState returns bottom.
If you then press Home to go to the top of the page, the scroll event changes the state from bottom to false, which leaves the affixed element positioned incorrectly.
If you then fire a dummy scroll event via $(document).trigger('scroll'), the state changes from false to top, which corrects the affixed element's position.

[mdo]

Bootstrap 3 is no longer being officially developed or supported.

All work has moved onto our next major release, v4. As such, this issue or pull request is being closed as a "won't fix." For additional help and support, we recommend utilizing our community resources. Thanks for your understanding, and see you on the other side of v4!

<3,
@mdo and team