Reading their reasonings in the reg article, they should allow use of the new
Silica Webview, provided it is used with the user's browser profile. After all,
it is just an embeddable version of the main browser, rather than a classic
webview. Maybe it should have its name changed...
On Sun Oct 16 17:28:06 2016 GMT+0200, Kimmo Lindholm wrote:
> But that should start for new ones on 20th oct, and full blockage april 2017 ?
> So you should be still fine.
> (this is not helping you problem though)
> From: Devel [mailto:devel-boun...@lists.sailfishos.org] On Behalf Of Oleg
> Sent: 16. lokakuuta 2016 17:28
> To: Sailfish OS Developers
> Subject: Re: [SailfishDevel] SilicaWebView, google sign-in button and app
> I don't know, but
> 2016-10-16 16:43 GMT+03:00 Slava Monich <slava.mon...@jolla.com>:
> Please excuse my ignorance but how can the server possibly tell the
> difference between the browser and a webview sending exactly the same HTTP
> requests? Just curious.
> There is no working solution because google prohibited oauth authorization
> via webviews
> 2016-10-16 15:02 GMT+03:00 <jollail...@gmail.com>:
> Care to share your code?
> Oleg Linkin kirjoitti ma lokakuuta 10 09:08:52 2016 GMT+0300:
> > Hello developers.
> > I try to implement authorization via google in my applications but I have
> > one problem.
> > In sailfish browser authorization works the next way:
> > Click on google sign-in button
> > Open new page with google authorization
> > Denied/Grant permissions to app
> > Page closed automatically
> > Page with google sign-in button reloaded automatically
> > But in webview the last 2 steps doesn't work. Does anybody has ideas how I
> > can do this?
> > Thx
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Sent from my Jolla
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org