First, I want to emphasize that you really should use https when processing user credentials. If you can, get an SSL certificate and serve your content over https . Using HTTPS, you can prevent MiTM attacks and user information leaks.
Aside, there are a number of potential sources of warning:
If you use the login button from a page serving HTTP instead of more secure HTTPS, sometimes communication with the login servers is blocked. If the input sometimes works and sometimes not, this may be the reason.
JavaScript (http/https) , Google (http://yoursite.com, https://yoursite.com)
JavaScript (, .com , yoursite.com), OAuth .
( ) Google, , .
, , , :
- cookie
'single_host_origin' 'http://yoursite.com'. - , http://.
- , , cookie .
- Chrome, , .
- , , (,
<script src="https://foo.bar/include.js" /> <script src="//foo.bar/include.js" />)