Won't authorize with current Chromium Build

[vurral]

Hi!

Thanks for your great plugin!

I wanted only to mention that Authorizing is not working with the newest Chromium Build (Version 31.0.1632.0 (223389))

After clicking on "AUTHORIZE WITH LAST.FM" I'm being redirected to the last.fm site, but after clicking on "Yes, allow access" I'm landing on about:blank and the authorization wasn't successful.

Im mentioning it to point to a possible bug in future releases. (It works for me on the current Chrome Build flawlessly!)

Keep up your great work!

[cgravolet]

Thanks for the heads up. Le sigh ;)

[ghost]

Any news on that bug, because Chrome 31 is in Beta now and the issue described above is still one.

Trying to authorise with Last.fm leads to an empty page. Last.fm recognise scroblr but scroblr doesn't recognise the fact that the authorisation is complete.

[cgravolet]

Well, the problem is that chrome botches the redirect from last.fm to the access-granted page. You can manually copy/paste the redirect URL from the last.fm 'allow access' screen, so the URL that scroblr sends is correct, however when last.fm tries to redirect to that page with the access token that scroblr needs to create a session, chrome just throws up a blank screen...

I'm not entirely sure what I can do, if anything, in scroblr to fix this issue since it seems to be a problem with chrome itself. However, I haven't spent that much time focusing on it, as it's a beta application so I'd rather not spend a lot of time debugging a chrome issue if it will most likely get fixed before it becomes stable.

It could be possible they put some sort of new restriction that stops sites from redirecting to local resources seeing as I don't pay much attention to the chrome beta releases, in which case I'll need to redo the entire authentication system... I guess now would be a good time to look into that.