Andrew Dodson

Hi @bolicd there is a little confusion in how your using `display:page`. Any `hello.login` promise with this option, i.e. `.then(success, fail)` handlers, wont be resolved as the entire window gets...

Please contribute to the next iteration https://github.com/MrSwitch/hello.js/pull/485:)

Install the next version... ``` npm i hellojs@next --save ```

@murbanowicz you should be able to do that already, ``` // Core const hello = require('hello/dist/hello.js`); // Set's global object // Modules require('hello/src/modules/google'); // uses global object, no need to...

If the resource presents has defined a content security policy for the request being made then modern browsers will throw this exception. Is this one of the existing services? What...

Hi @mharrcgs That seems to be a separate issue, and would occur if you've defined a redirect_uri to be on a different origin from your application

Your assumptions all seem spot on. Can you determine the page from which the error is triggered? Also consider using `display: "page"` option.

This is not the best, but the in current version 1.x this is how the auth response is saved in the client... ```js hello.utils.store('facebook', {access_token:'abc...xyz', ...}) ```

Hi Raheel that's great. However I can't merge it without a pull request. Thanks

That's fine, the oauth-proxy settings can easily be modified to enforce that a passthru requests. Thanks On 5 Feb 2015 00:34, "Raheel Hsn" [email protected] wrote: > The reason I didnt...