You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On every page the footer stays at the position where it'd be at the bottom of the screen without having scrolled, i.e. when I scroll down the footer stays in the middle of the page.
Steps to reproduce the bug
Go to any page of any instance, this one for example.
Scroll down a bit.
The footer stays at the same place, writing over content in the middle of the page.
For context I am running Firefox ESR 128.8.0.
What's the expected behavior?
When I scroll down I expect the footer to stay at the bottom of the page.
Additional context / screenshot
I checked that the instance that this was reported on is running the latest git commit, or I can reproduce it locally on the latest git commit
The text was updated successfully, but these errors were encountered:
I remember this used to be an issue that was fixed at some point, not sure what would cause it to happen again.
I can't get it to happen for myself even on firefox esr though.
That pull request also changes the behavior of the footer. Right now it's (supposed to be) always at the absolute bottom of the page, but the pull request changes it to always be visible at the bottom of the screen.
Are you using a layout other than card? I can get bad behavior with the footer not being at the bottom of the screen on on clean and compact when there's very little content.
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
On every page the footer stays at the position where it'd be at the bottom of the screen without having scrolled, i.e. when I scroll down the footer stays in the middle of the page.
Steps to reproduce the bug
For context I am running Firefox ESR 128.8.0.
What's the expected behavior?
When I scroll down I expect the footer to stay at the bottom of the page.
Additional context / screenshot
The text was updated successfully, but these errors were encountered: