adaliabooks: XD
It's ok, I think I've found the problem. GoG seems to have disabled debuging, which is how I get all my scope info to do stuff.
Thankfully there are ways to re-enable it, just trying to find the best one.
Thanks
mrkgnao: When you have some time, could you please share this debugging information you talk about? How you get it, what it offers, etc. Might be useful to know.
Let's see how this change affects MaGog. Next run in three hours.
Well, I didn't really realise it was debug information, but looking into why it doesn't work now that seems to be the reason.
GoG runs on AngularJS (or the new bits do anyway), I don't understand all of how Angular works yet (though I'm getting there) but the most useful thing you can do is get the information used to show the various information (game details etc.)
If you look at the source of the account page you'll see a lot of references to things like {{ product.id }} which when compiled by Angular turns into the id of the referenced product (or the title, or the image whatever variable is needed)
I can see what these variables are (and make use of them or change them) by calling:
angular.element(document.querySelectorAll('.list')).scope();
to retrieve the scope of any particular element on the page.
In chrome you can use:
angular.element($0).scope();
To get the scope of the element currently selected in the inspector.
It's all pretty interesting, though very confusing too as lots of the info is duplicated all over the place.
If you don't interact with Angular, it shouldn't have any effect on MaGoG I would think.