REVIEWS
========
When loading a game page, the following is printed to console:
- Settings Initilised adaliaf...user.js (line 29)
- AF-style setting changed adaliaf...user.js (line 29)
- navbar-fundamentals-position setting changed adaliaf...user.js (line 29)
- Features Loaded adaliaf...user.js (line 29)
- /game/planescape_torment adaliaf...user.js (line 29)
- Game Page adaliaf...user.js (line 29)
- Loading Reviews Filter adaliaf...user.js (line 29)
- ReferenceError: angular is not defined adaliaf...user.js (line 1832)

DOWNLOADER LINKS
==================
When loading one's library page, the following is printed to console:
Relative positioning of table rows and row groups is now supported. This site may need to be updated because it may depend on this feature having no effect. [probably unrelated]
Settings Initilised adaliaf...user.js (line 29)
AF-style setting changed adaliaf...user.js (line 29)
navbar-fundamentals-position setting changed adaliaf...user.js (line 29)
Features Loaded adaliaf...user.js (line 29)
/account adaliaf...user.js (line 29)
Account adaliaf...user.js (line 29)

When clicking on a game in one's library, nothing whatsoever is printed to console.

Mozilla is getting rid of the old extension APIs and moving to a Chrome compatible API in the future and have put a timeline of about 18 months until the old interfaces are removed. The take home is that all extension developers will have to update their extensions to the new interfaces to remain compatible with Firefox by then, but the upside is that it makes it easier for developers to write cross-browser extensions. It's a controversial change but they've committed to it as it was deemed a necessary requirement for Electrolysis a.k.a multi-process Firefox which is an up and coming feature being developed for 6+ years now.

In short, at some point in the next 18+ months or so all extensions etc. should be cross browser or should be minimal effort to port between browsers due to the same APIs, or they'll need to be ported or end up incompatible. For greasemonkey/stylish scripts and the like, I'm not sure what will need to happen but devs will probably be anticipating that and converting/porting code as needed. So within a couple years extensions/scripts in theory might end up being a single standard of sorts and available cross-browser. :)

Thanks for that, it looks like the same error the review filter had. Just need to wrap the functions in timeouts to give angular time to load so it can assign the variable properly, hopefully that might fix both of them as the download links are reliant on angular now too.

Two suggestions, if possible
1) Give us the option of having both web downloads and gogdownloads. For quick checks, I prefer using the web downloads, and having to reload the page if I forgot to switch is a bit annoying (though nothing I can't live with).
2) Add a link to this forum thread in the fundamentals menu, to make it easier to find it and post when required.

Either way, thank you for the scripts.

Yeah, I'm planning to put a switch on the gamecards like there used to be, so you can switch between them at will.

I'll add a link to the thread, good idea.

Having trouble getting it to work on Firefox, unfortunately while it seems to be the same problem I had with the reviews filter script the solution I used there doesn't seem to work... and Firefox is rubbish at actually telling me what's wrong (the "ReferenceError: angular is not defined" is gone when I add a timeout but the script seems to just fail silently at the same point instead..)

We're getting there... slowly but surely...

Downloader links are now working in Firefox (there's no proper official update, but if you force an update in GreaseMonkey they should work)

But the review filter is still proving a pain.. I have at least isolated the problem, which boils down to GM's security sandbox stuff. Basically because this script saves stuff (your settings and preferences) it cuts off my access to important variables on the page. I've managed to regain said access, but a lot of the bits I'm using to make the reviews section work are no longer working... and I'm not yet sure why...
Might have to call it a day on it for now and come back with fresh eyes tomorrow and see if I can make further progress.

In the meantime, I would suggest you all use Chrome instead because it works perfectly there and GoG is really slow on Firefox anyway (I'm only joking, mostly ;P)

This starts to sound as if you've been secretly hired by GOG.


Take your time, I'm sure everyone can wait a bit longer, and in any case, the separate scripts still work just fine.

Good show. One step at a time. I am sure that with time you will realise your mistake and discard Chrome in favour of Firefox.

Meanwhile, downloader links subscript indeed works. Great. Time to disable it in the options (as I don't use the downloader).

Take your time.

I'm beginning to understand why GoG finds it so hard to make things work on Firefox...

True. Thanks :)

:P
Not likely.

That's the idea, configurable :)

I take it that means we can't have both?

Thanks for the script, adaliabooks! I'm looking forward to the update which will make it work properly in Firefox. =P

I hadn't heard this but this is a very good move considering that Opera also supports the Chrome API.

Yep, I should point out that Opera uses Chrome's web engine (Blink/Webkit) so they're essentially just Chrome with a different browser shell around the core engine. Mozilla is not doing that though, they'll remain an independent browser with their own independent engine (Gecko), but they're just developing a new extension interface around a common standard which I believe is being coined "Web Extensions" or something like that. It has its pros and cons which have spawned controversy, but there's time between now and then with which they have plenty of time to address developer concerns. It mainly surrounds the fact that the existing Mozilla extension APIs are infinitely more powerful than Chrome's and developers fear their extensions wont be able to be ported to the new interface as it isn't as flexible due to not exposing all of the same browser internals. Mozilla intends to address that wherever possible by developing and enhancing the API to try to accommodate features needed by existing extensions. Hopefully they're able to do that over the next 18 months or there will be some unhappy people. :) Overall their goals are very well grounded though even if there are some growing pains along the way. I've got mixed feelings about it all personally but a default positive outlook. :)

Not at the moment, but adalia plans to add a switch to each game's download window, like in the good old days (before they became god.com).

Wow, great info. I just hope Firefox can bring its rendering speed up. Used to be the fastest browser out there by a long shot, then it kept getting more and more bloated. It's gotten a little speedier over the last 6 months or so, but not enough to knock off Chrome. Firefox used to be absolute favorite browser, but when Chrome came out of beta and couple versions after, wow that lightning speed rendering and Chrome's searchbar... I hate that it's Google, I hate PepperFlash, but FireFox still has a bit of a way to go to win me back over. I hope they do, because I'm a big fan of Mozilla and have been pretty much since day 1. I really wish they would overhaul Thunderbird, though.