finkleroy: It appears all that needs to be disabled in Barefoot Essentials is the last option in the bugfixes menu (keep the footer at the bottom of the page). No need to disable the entire script. The issue I was having with the bottom of the page and also the issue of not being able to start a conversation with someone by hovering the mouse over their name in the forum have both been fixed. Thanks to HypersomniacLive for figuring out how to fix it.
Oh, is that what that option does? I don't use either of those scripts, but I saw in the Barefoot Essentials thread that people recommended unchecking the last option, without mentioning what the option was about at all.
Personally, I use a personalized stylesheet. It's just a Cascading Style Sheet (CSS) file.
What I noticed a moment ago was that the footer was not minimized. I have it pretty much completely collapsed with CSS so it doesn't take up more than one line of space: reedem code, contact us, etc. When I hover the mouse over that part then the footer will be displayed below it, but I'll only see it if I then scroll the page. So it never takes up space until I want it to.
But today for some reason the footer wasn't at the bottom of the screen, it was displaced from the bottom. I checked the webpage HTML sources and my styles, and it turns out the classes changed for the selecting the element classed as "content". That element used to be inside another element classed as "wrapper", so the selector I used to have was:
[ng-app="gog"] .wrapper>.content
However, the element classed with "content" is now also classed with "wrapper" instead of contained by another element (classed as "wrapper"). So I changed the selector it to simply:
[ng-app="gog"] .content
In essence, just referencing the element classed as "content" without requiring it be within another element classed as "wrapper" anymore. I'm not sure if that will be enough, because there might be other elements also classed as "content". Didn't see anything, but there's too much HTML for me to care enough to be sure. If that turns out to not be enough for other GOG webpages (besides front page and forum, so far), then I'll likely make it ".wrapper.content", which would find that element by requiring both classes on it. But so far just "content" works.
Perhaps the Barefoot Essentials script was expecting a similar structure, that of "wrapper" > "content" instead of "wrapper and content"? Sort of off topic, but perhaps that info might be of use. Of course, the change to the webpages might have been temporary, or maybe GOG is restructuring or simplifying the webpages. *shrug*