976749 - Missing connect button in main google page in certain locales

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect, P1)

Description

[Ioana Chiorean]

Tracking missing connect button issues

Comment 1

[Karl Dubost💡 :karlcow]

We should avoid to open xxx bugs for the same issue. Let's just open one. All the locales in Google case is controlled by the same code base at Google.

Comment 8

[Ioana Chiorean]

(In reply to Karl Dubost :karlcow from comment #1)
> We should avoid to open xxx bugs for the same issue. Let's just open one.
> All the locales in Google case is controlled by the same code base at Google.

Thanks for the advice Karl - will keep that in mind. I was about to dupe them now - Thanks for doing that! Sorry.

Comment 9

[Hallvord R. M. Steen [:hallvors]]

This bug sounds very similar to bug 976753 - same feature, quite possibly same code? But it's up to you whether to keep it different or dupe one of them :)

Comment 10

[Karl Dubost💡 :karlcow]

Attachment: google-locales-connect.jpg

Not sure it is exactly the same bug, but related for sure. 
The one in Bug 976753 is talking about truncated text.
This one is talking about missing connect button.

But we indeed get weird results. See these screenshots gained by sending with these parameters from Japanese geolocated IP 

User-Agent:      Mozilla/5.0 (Android; Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
Accept:	         text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language:	 en-US,en;q=0.5

to 

* google.ru     Received russian Google with connect button
* google.me     Received russian Google without connect button
* google.co.jp  Received Japanese Google with connect button


:) inconsistencies. I wonder if we hit different servers at Google.

Comment 11

[Hallvord R. M. Steen [:hallvors]]

There's oddly enough something server-side that determines this. All servers send the CSS for the "signin-link" button but some of them do not always send the markup for the button. This is the markup:

<a class="signin-link" href="https://accounts.google.com/ServiceLogin?continue=http://www.google.pl/%3Fzx%3D1400071546&amp;btmpl=mobile_tier2&amp;hl=pl"> 

I could not quite figure out what the logic was, but it is most likely depending on UA sniffing.

Comment 12

[Karl Dubost💡 :karlcow]

Pinged Google about it.

Comment 13

[Karl Dubost💡 :karlcow]

In sites, not sending the connect button, the div#gbr is not sent at all.
btw same issue with Firefox OS.

When emulating the Chrome Mobile UA, this is what we receive for the same site (Here google.me)

<div id="gbr"><div id="gbv" class="gbvlo"><ol class="gbtc"><span id="gbvsi"><li class="gbt"><a target="_top" href="https://accounts.google.com/ServiceLogin?hl=sr-ME&amp;continue=http://www.google.me/" onclick="gbar.logger.il(9,{l:'i'})" id="gb_70" class="gbgt"><span class="gbgs4"><span id="gbi4t">Prijavite se</span></span></a></li></span><span id="gbvbp"><li id="gbp2" class="gbt"><a class="gbgt" id="gbg5" aria-haspopup="true" aria-owns="gbd5">  <span class="gbgs4"><img id="gbi5i" onerror="window.gbar&amp;&amp;gbar.pge?gbar.pge():this.loadError=1;" src="//ssl.gstatic.com/gb/images/silhouette_24.png" alt=""><span class="gbmai"></span><span class="gbmab"></span><span class="gbmac"></span>  </span></a><div class="gbm" id="gbd5" aria-owner="gbg5"><div class="gbpc"><span id="gbpbe" class="gbps2"></span></div><div class="gbmpalb"><a target="_top" id="gbpso" role="button" onclick="gbar.logger.il(9,{l:'o'})" href="https://accounts.google.com/Logout?hl=sr-ME&amp;continue=http://www.google.me/" class="gbqfba">Odjavite se</a></div></div></li></span></ol></div></div>

As of today this is still not solved.
This is a strange issue in the sense that it removes opportunities for Google to have more logged customers.

Comment 14

[Karl Dubost💡 :karlcow]

And here the difference in between a site receiving the button for 

FOR FIREFOX ANDROID
<div id="gbr"> <div id="gbv"> <a class="signin-link" href="https://accounts.google.com/ServiceLogin?continue=http://www.google.fr/%3Fzx%3D1408341922&amp;btmpl=mobile_tier2&amp;hl=fr"> <div>Connexion</div> </a>   </div> </div>


AND CHROME MOBILE
<div id="gbr"><div id="gbv" class="gbvlo"><ol class="gbtc"><span id="gbvsi"><li class="gbt"><a target="_top" href="https://accounts.google.com/ServiceLogin?hl=fr&amp;continue=http://www.google.fr/" onclick="gbar.logger.il(9,{l:'i'})" id="gb_70" class="gbgt"><span class="gbgs4"><span id="gbi4t">Connexion</span></span></a></li></span><span id="gbvbp"><li id="gbp2" class="gbt"><a class="gbgt" id="gbg5" aria-haspopup="true" aria-owns="gbd5">  <span class="gbgs4"><img id="gbi5i" onerror="window.gbar&amp;&amp;gbar.pge?gbar.pge():this.loadError=1;" src="//ssl.gstatic.com/gb/images/silhouette_24.png" alt=""><span class="gbmai"></span><span class="gbmab"></span><span class="gbmac"></span>  </span></a><div class="gbm" id="gbd5" aria-owner="gbg5"><div class="gbpc"><span id="gbpbe" class="gbps2"></span></div><div class="gbmpalb"><a target="_top" id="gbpso" role="button" onclick="gbar.logger.il(9,{l:'o'})" href="https://accounts.google.com/Logout?hl=fr&amp;continue=http://www.google.fr/" class="gbqfba">Déconnexion</a></div></div></li></span></ol></div></div>

Comment 15

[Karl Dubost💡 :karlcow]

The issue is still the same:

All these properties do not get the Connect button. Be with Firefox OS or Firefox Android.
* google.me
* google.kz
* google.mk
* google.mn
* google.tn
* google.so

Opera Blink doesn't receive the mobile version for some of them while Opera Presto does.
Windows Phone seems to be receiving the same version than us.

Candidate for Webcompat.com

Comment 16

[Karl Dubost💡 :karlcow]

google.me has  a choice of languages. If we choose English or српски, we get the sign-in button
google.kz if we choose English or русском. we get the sign-in button
google.mk English
google.mn English
google.tn no sign in which ever language English, French, Arabic
google.so Arabic and English get the sign in

Note that Google Chrome provide the login for all languages.

Comment 17

[Mike Taylor [:miketaylr]]

Seems like a variation on Tier 1 search issue.

Comment 18

[Sergiu Logigan [:sergiu]]

Tested with google.kz and google.mk on Google Pixel (Android 8.1.0) - 1080 x 1920 pixels (~441 ppi pixel density) and Release 61.
I can still reproduce this one.

Mike, Is it worth contacting Google about this?

Comment 19

[Mike Taylor [:miketaylr]]

(In reply to Sergiu Logigan [:sergiu] from comment #18)
> Tested with google.kz and google.mk on Google Pixel (Android 8.1.0) - 1080 x
> 1920 pixels (~441 ppi pixel density) and Release 61.
> I can still reproduce this one.
> 
> Mike, Is it worth contacting Google about this?

Yeah, I think so. Or rather, re-ping (see https://bugzilla.mozilla.org/show_bug.cgi?id=976749#c12).

Karl, can you reach out to Google again?

Comment 20

[Karl Dubost💡 :karlcow]

Re-contacted today. Thanks.

Comment 21

[Firefox Bug Husbandry Bot]

See bug 1547409. Moving webcompat whiteboard tags to keywords.

Comment 22

[Raul Bucata]

It seems that the issue has been fixed, as I was not able to reproduce the issue. The connect button (Sign in) is present:

https://prnt.sc/soo2DZK33de-

Karl, could you please confirm this?

Tested with:

Browser / Version: Firefox Nightly 100.0a1 (2015869419 -🦎100.0a1-20220317092857🦎)
Operating System: Samsung A51 (Android 11) -1080 × 2400 pixels 20:9 aspect ratio (~405 ppi density)
Operating System: Google Pixel 3 (Android 12) -1080 x 2160 pixels, 18:9 ratio (~443 ppi density)

Comment 23

[Karl Dubost💡 :karlcow]

confirmed.