It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Thanks for the fix.
On my SRWare Iron (Chrome fork), the line that displays the pages at the bottom gets hidden by the collapsed footer when the option "Smaller space before the footer" is enabled. When disabled, things look and behave exactly as on Firefox with the option enabled.

Don't know if it's only me, a SRWare Iron issue or a general Chrome-engine one.
avatar
HypersomniacLive: On my SRWare Iron (Chrome fork), the line that displays the pages at the bottom gets hidden by the collapsed footer when the option "Smaller space before the footer" is enabled. When disabled, things look and behave exactly as on Firefox with the option enabled.

Don't know if it's only me, a SRWare Iron issue or a general Chrome-engine one.
It's a chrome engine one. I mentioned it in the "what just broke" thread a while back and it was confirmed to be some sort of Chrome specific bug (the problem is actually that the size of the space between the posts and the footer changes depending on which post you last hovered over, and the BE fix only works half the time and breaks it the other half)
avatar
adaliabooks: It's a chrome engine one. I mentioned it in the "what just broke" thread a while back and it was confirmed to be some sort of Chrome specific bug (the problem is actually that the size of the space between the posts and the footer changes depending on which post you last hovered over, and the BE fix only works half the time and breaks it the other half)
I'm not sure it's that bug. It's happening consistently for me - with the option ticked, there's no space whatsoever before the footer, hence why the collapsed footer is directly under the last post. And hovering or not over any post doesn't seem to be involved - I get it even when just opening a page and scrolling down using the browser's vertical scroll bar.

It's no big deal for me, as I don't use that browser for anything much really, and, as I said, unticking the option made things look and work the exact same way they do in Firefox with the option enabled. Which seems to imply that in Chrome-engine based browsers, or at least in my SRWare Iron, the default space before the footer is not as large as in Firefox.


EDIT: typo
Post edited February 16, 2016 by HypersomniacLive
avatar
HypersomniacLive: I'm not sure it's that bug. It's happening consistently for me - with the option ticked, there's no space whatsoever before the footer, hence why the collapsed footer is directly under the last post. And hovering or not over any post doesn't seem to be involved - I get it even when just opening a page and scrolling down using the browser's vertical scroll bar.

It's no big deal for me, as I don't use that browser for anything much really, and, as I said, unticking the option made things look and work the exact same way they do in Firefox with the option enabled. Which seems to imply that in Chrome-engine based browsers, or at least in my SRWare Iron, the default space before the footer is not as large as in Firefox.

EDIT: typo
Hmm, maybe not then. Odd that you're not getting it though as all the other Chrome based browsers seemed to be...
But I think the fix was originally intended for Firefox, where the space is always larger, so without the aforementioned bug in Chrome (or Chrome based browsers) you just shouldn't need the fix at all (as you've found)
avatar
adaliabooks: Hmm, maybe not then. Odd that you're not getting it though as all the other Chrome based browsers seemed to be...
But I think the fix was originally intended for Firefox, where the space is always larger, so without the aforementioned bug in Chrome (or Chrome based browsers) you just shouldn't need the fix at all (as you've found)
My SRWare Iron may well suffer from the bug you reported, and I just haven't noticed it since it's not my default browser.


avatar
adaliabooks: [...]

But I think the fix was originally intended for Firefox, where the space is always larger, so without the aforementioned bug in Chrome (or Chrome based browsers) you just shouldn't need the fix at all (as you've found)
If that's indeed the case, I will be nice and refrain from commenting on what that tells about GOG and their web devs. ;-)
New update: version 2.4

-New feature: option to force HTTP links in navigation bar
-New feature: replace ACCOUNT menu text with username
-Compatibility fix: now sends correct join date to GOGWiki when syncing
avatar
Azhdar: How to disable HTTPS? Recent update uses https as default, I want to restore http mode.
avatar
PookaMustard: Again, thank you, paladin181 and thank you too, Barefoot_Monkey! Now I have to fix this little join date bug, because I joined on the 1st of January 1970 :/.
avatar
HypersomniacLive: Question - how hard would it be to add back our avatar and username on the account tab? GOG has not responded to inquires about why they scrapped it, even though it made it into Galaxy which tells me they have no intention of bringing it back on the site.
Thanks for the suggestions :)

Greasemonkey and Tampermonkey users should receive the update automatically. I'll probably send the Chrome extension up to Google tomorrow after I have a chance to test it thoroughly.
Post edited February 19, 2016 by Barefoot_Monkey
avatar
Barefoot_Monkey: New update: version 2.4

-New feature: option to force HTTP links in navigation bar
-New feature: replace ACCOUNT menu text with username
-Compatibility fix: now sends correct join date to GOGWiki when syncing
Oh, shiny! Updating as soon as I hit the "submit quick post" button!

And thank you!



avatar
Barefoot_Monkey: [...]

-New feature: replace ACCOUNT menu text with username

[...]
Either I don't understand what this does, or it's not working for me - it still says "ACCOUNT" in my tab. :-(
Post edited February 19, 2016 by HypersomniacLive
avatar
Barefoot_Monkey: [...]

-New feature: replace ACCOUNT menu text with username

[...]
avatar
HypersomniacLive: Either I don't understand what this does, or it's not working for me - it still says "ACCOUNT" in my tab. :-(
Works in HTTP, but not in HTTPS.
avatar
Barefoot_Monkey: New update: version 2.4
THANK YOU!!
Post edited February 19, 2016 by mrkgnao
avatar
mrkgnao: Works in HTTP, but not in HTTPS.

[...]
*sad panda*


Cheers for the update nonetheless, Barefoot_Monkey!
avatar
mrkgnao: Works in HTTP, but not in HTTPS.

[...]
avatar
HypersomniacLive: *sad panda*
I assume it's a bug which BM will be fixing.
avatar
mrkgnao: I assume it's a bug which BM will be fixing.
I'm pretty sure myself, I just got a bit excited about getting that bit back.
avatar
HypersomniacLive: *sad panda*
Cheer up, panda - Version 2.4.1 is up with a fix for that :)
avatar
Barefoot_Monkey: Cheer up, panda - Version 2.4.1 is up with a fix for that :)
*happy panda*

♪♬ ┏(・o・)┛♫♪
avatar
HypersomniacLive: *sad panda*
avatar
Barefoot_Monkey: Cheer up, panda - Version 2.4.1 is up with a fix for that :)
*ecstatic kitten*

♪♬ ┏(・o・)┛♫♪