668275 - GMail sends a imperfect version to Firefox for Android

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect)

Description

[Thomas Arend [:tarend]]

Attachment: GMail mobile and touch versions in Firefox for Android

There are several issues with GMail in Firefox for Android:

(1) GMail shows the simple version instead of the touch version
(2) When forced into the touch version (using Phony add-on set to "Android") the layout is really broken, icons are busted, which makes the page unusable.

Perhaps, those layout issues could be related to WebKit-specific code in the HTML / CSS. See https://bugzilla.mozilla.org/show_bug.cgi?id=668218

Comment 1

[Wesley Johnston (:wesj)]

This and bug 668218 are caused by Google supporting on -webkit- prefixed css on these pages (i.e. no fallbacks for anyone). From what I remember, their other complaint had to do with image resizing which we have since fixed. I'm not sure what we can do besides continuing to reach out to them. Public blog posts? We could write an addon that dynamically rewrites Google pages to use standards?

Comment 4

[Jason Smith [:jsmith]]

Gmail is both a top site/app. Not having it function properly on mobile gecko can negatively affect B2G (if it allows gmail as an app) and Fennec Native. Nominating for kilimanjaro, as this relates to mobile web compatibility.

Comment 5

[Kev Needham [:kev]]

Who's going to take lead on this? I can reintroduce Google contacts, but they had a number of concerns which needed to be addressed before they considered redirecting to the touch version (some of which are prefixing, so that's a big question mark).

Comment 6

[Lawrence Mandel [:lmandel] (use needinfo)]

Jason is taking the lead on Google properties from a QA perspective. Can you please send the list of concerns so that we can be sure to address as many as possible before getting in touch with Google? It will also be very helpful to have introductions once we're ready for them.

Comment 7

[Aaron Train [:aaronmt]]

As if June 14th, 2012 - they are now serving a sub-optimal basic HTML version. As I understand it, we're really pushing for their touch-webkit based version.

Comment 8

[Justin Wood (:Callek)]

(In reply to Lawrence Mandel [:lmandel] from comment #6)
> Jason is taking the lead on Google properties from a QA perspective. Can you
> please send the list of concerns so that we can be sure to address as many
> as possible before getting in touch with Google? It will also be very
> helpful to have introductions once we're ready for them.

(In reply to Aaron Train [:aaronmt] from comment #7)
> As if June 14th, 2012 - they are now serving a sub-optimal basic HTML
> version. As I understand it, we're really pushing for their touch-webkit
> based version.

Can we get traction here, this surely does make GMail-Mobile unusable for me. And I'm happy to assist in any way here.

FWIW With the Galaxy S3, Aurora Firefox, it is the desktop version afaict. And waaay too small to read without manually zooming. No option to even switch to mobile-non-touch version.

Comment 10

[Yves Dessertine]

Hi.

Found this workaround : visit https://mail.google.com/mail/mu/
Looks like a fully functional mobile GMail (tested on current Aurora and Nightly), see attachment

Comment 11

[Yves Dessertine]

Attachment: Workaround : visit https://mail.google.com/mail/mu/

Workaround : visit https://mail.google.com/mail/mu/
Looks like a fully functional mobile GMail (tested on current Aurora and Nightly)

Comment 12

[alex_mayorga]

Still a problem on today's Nightly so marking as "Trunk".

Is there a GOOG's e-mail we can send friendly reminders to?

Comment 13

[Lawrence Mandel [:lmandel] (use needinfo)]

We are in touch with Google and they are aware of the problem. While we're pushing on a fix, the fix involved more than simply recognizing Firefox mobile UAs. GMail makes use of WebKit specific features and must be updated to function in Firefox.

Here is at least one other method that I found with a quick search that may reach the GMail team. (I'm don't have a direct feedback link):
https://survey.googleratings.com/wix/p5092995.aspx?referral_code=GmailGPForm01

Comment 14

[Sunil]

(In reply to Yves Dessertine from comment #11)
> Created attachment 717485 [details]
> Workaround : visit https://mail.google.com/mail/mu/
> 
> Workaround : visit https://mail.google.com/mail/mu/
> Looks like a fully functional mobile GMail (tested on current Aurora and
> Nightly)

I am not seeing the same results either (I tried FF 23 aurora with user agent set to Fennec 9.0).

Comment 16

[Swarnava Sengupta (:Swarnava)]

Its Working FIne now for me with Firefox 25 beta

Comment 17

[Sunil]

Can you please tell me what's the user agent string you used And what shows up, the mobile version, tablet or the desktop version?

Thanks.

Comment 18

[Sunil]

I tried the User agent 'Mozilla/5.0 (Android; Tablet; rv:24.0) Gecko/24.0 Firefox/24.0' on my Firefox 25 and I got the desktop version and NOT the tablet version. 

If my test was wrong, please let me know the correct user agent to try, else I think this bug should be kept open.

Comment 19

[Swarnava Sengupta (:Swarnava)]

Attachment: 2013-09-28_21-10-05.jpg

Mozilla/5.0 (Android; Tablet; rv:25.0) Gecko/24.0 Firefox/25.0

Comment 20

[Sunil]

To me that looks like a mobile version and not a tablet version.

Comment 21

[Vincent]

@Swarnava Please mark this bug as UNRESOLVED. See the difference between [1] and [2]. The former is what it currently looks like in Firefox (apparently for you too), the latter is what it should look like.

[1] http://imgur.com/60wmJOl
[2] http://imgur.com/5CzIxTZ

Comment 22

[Swarnava Sengupta (:Swarnava)]

(In reply to Vincent from comment #21)
> @Swarnava Please mark this bug as UNRESOLVED. See the difference between [1]
> and [2]. The former is what it currently looks like in Firefox (apparently
> for you too), the latter is what it should look like.
> 
> [1] http://imgur.com/60wmJOl
> [2] http://imgur.com/5CzIxTZ

Yes you are right, i just compared GMAIL with UC browser.

Comment 23

[Karl Dubost💡 :karlcow]

So the issue with tier1 version is common for Google services/Mobile Firefox. It is most of the time unlikely we will get a fix, if it involves more than User Agent redirections, aka sniffing. If someone to spend time on analyzing what would be the proper CSS to address the issues (I suspect webkit flexbox), then it might help to get it solved. But don't keep your hopes too high.


Some of the current bug. We have a direct line with Google, but not a direct line with all individual products and offering the tier1 to other non-WebKit browsers is not their priority (even sometimes for WebKit browsers)
https://bugzilla.mozilla.org/buglist.cgi?f1=bug_file_loc&list_id=9624148&o1=allwordssubstr&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=google&component=Mobile&product=Tech%20Evangelism

Comment 25

[Karl Dubost💡 :karlcow]

OK. This morning I had to dig a bit more in the issue because of Bug 967149.

Currently Firefox OS and Firefox Android are receiving a very basic version of GMail. It's barely usable on Firefox OS with a small screen and fat fingers.

When accessing https://mail.google.com/mail/mu/ with Firefox OS and Firefox for Android UA, the browser are redirected to an Error 403 page.

But where it starts to be interesting is that accessing https://mail.google.com/mail/mu/ with the Firefox Desktop User Agent is (mostly) working. Most of the features are working except for a few glitches. 

Could someone double test on Firefox OS and Firefox Android by faking the UA to be desktop?
https://mail.google.com/mail/mu/

That's good news. 
Because, if it's just a matter of redirection, we can ask google to point us here instead of there.

Comment 26

[Vincent]

https://mail.google.com/mail/mu/ looks good on first sight on my Firefox for Android with the Firefox Desktop US string. I haven't tested it extensively, though, and at least the menu buttons on top when viewing an individual email do not work.

Comment 27

[Chris]

https://mail.google.com/mail/mu/ appears mostly correct using the desktop FF UA. As Vincent stated, the buttons on individual email messages (Menu/Archive/Reply/Trash...)  do not work at all, and are out of place. They are buried under other icons in a corner of the screen.

Comment 28

[gabriele.vidali]

Have you ever tried using gmail with firefoxos ?
The ui is almost ok now with b2g 2.1 but I can't reply nor forward any message.

See this http://imgur.com/mTS9Gra

Comment 29

[Saurabh Anand [:sawrubh]]

Gabriele, that error seems similar to what I get in Firefox for Android, when I am on a slow connection and pages fail to load. Do you get that similar error (like in the screenshot) when you're on a relatively fast connection too?

Comment 30

[Karl Dubost💡 :karlcow]

Gabriele, yes see Bug 1036987

Comment 31

[gabriele.vidali]

(In reply to Saurabh Anand [:sawrubh] from comment #29)
> Gabriele, that error seems similar to what I get in Firefox for Android,
> when I am on a slow connection and pages fail to load. Do you get that
> similar error (like in the screenshot) when you're on a relatively fast
> connection too?

No, I get that error even on fast connections.
YAHOO mobile mail works ok

Comment 32

[ricardo]

It's really amazing how anyone can solve this problem. When I read the posts, I see Mandingo and people trying to prove that the bug exists.

What is the difficulty to understand the problem? Not already been told that when it comes to https://mail.google.com/mail/mu URL appears an old version of GMAIL or a more primitive interface?

There is forecast to solve this? Using firefox on android with this pendenga?

Comment 33

[Kevin Brosnan [Ex-Mozilla]]

This is a issue that Mozilla cannot solve. 

Gmail is controlled by Google. It is up to Google to decide to provide a rich experience to Firefox mobile users. You can help by asking for support at the Google gmail support forum, https://productforums.google.com/forum/#!categories/gmail

Comment 34

[ricardo]

(In reply to Kevin Brosnan [:kbrosnan] from comment #33)
> This is a issue that Mozilla cannot solve. 
> 
> Gmail is controlled by Google. It is up to Google to decide to provide a
> rich experience to Firefox mobile users. You can help by asking for support
> at the Google gmail support forum,
> https://productforums.google.com/forum/#!categories/gmail

may be a problem with the Agent Browser, you can tell whether there is the option to set this up Firefox on Android?

http://www.useragentstring.com/pages/Browserlist/

Seriously that is owned by Google GMAIL? I swear I did not know that, thought it was well maintained by the foundation Firefox.

Comment 35

[Aubrey Anderson]

@ricardo & Kevin: for what it's worth, there are at least a couple problems to address both with Gmail specifically and to support a lot of other "mobile sites" out there.  The first one is probably pretty easy to solve: just present an alternate User Agent string.  If you spoof your user agent and make yourself appear as any popular mobile webkit stack when you hit gmail today, you will get the right content, at least.  And as noted several times above, it's a start.

The second problem is potentially harder, but *not* actually completely out of Mozilla's hands: gmail, as formatted for mobile browsers today, is full of "-webkit-whatever" CSS syntax for formatting and animations and it relies on some webkit-specific hooks in javascript, e.g. webkitTransitionEnd() and things like that.  Many many other "sites optimized for mobile" are doing this, too, unless they have thought ahead and used something clever like prefix free (http://leaverou.github.io/prefixfree).

Back when B2G initially spun up, some of us suggested the possibility of Gecko just saying screw it and supporting "-webkit-whatever" syntax in CSS as well as un-prefixed syntax and pointing prefixed events like webkitTransitionEnd at non-prefixed events like transitionEnd.  The fact that the prefix-free library does this with great success in 2k of JavaScript demonstrates pretty clearly that it's a viable way to go.  As it turned out though, supporting other prefixes was not a popular idea at Mozilla in 2012 (I was surprised, Brendan was even behind it), and here we are in 2014 still with no gmail support in Firefox on mobile devices and a dead-end feeling among Mozillians like they can't do anything about things like this.

Firefox was late to the mobile space and now a truckload of prefixed implementations are out in the wild, probably for good.  By not supporting them proactively in Firefox, you end up accidentally punishing Firefox users on mobile, making the problem worse and more confusing for regular people, and in turn driving them away from Firefox.  Gecko supporting other browser's prefixes would let people use Firefox on mobile devices for more things right away, decouple from whatever Google (or whoever else's) timeline is to broaden support, and let more people spend more of their mobile web time in Firefox which is ultimately what we want, right?  

And we could close this bug without additional "google evangelism," which would be great.

Comment 36

[Karl Dubost💡 :karlcow]

Attachment: gmail-fakeua.png

(In reply to misteranderson from comment #35)
> The first one is probably pretty easy to solve:
> just present an alternate User Agent string.  If you spoof your user agent
> and make yourself appear as any popular mobile webkit stack when you hit
> gmail today, you will get the right content, at least.  And as noted several
> times above, it's a start.

It doesn't work. :)
See the screenshot. This is with Chrome Mobile UA. 

I contacted Google again.

Comment 37

[Aubrey Anderson]

Actually that DOES look like it's working.  I use 

"Mozilla/5.0 (iPhone; CPU iPhone OS 6_1_4 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10B350 Safari/8536.25"

and can then navigate, see emails, go into the compose flow, etc on Firefox.  The point is that you're getting served the correct UI for mobile without entering a special URL because of the modified User Agent string and you're not getting served the IE version from 2003 which is what you get if you don't provide a user agent string that gmail recognizes.

The next problem is primarily with the CSS.  For instance, the star icons in your screen shot are gigantic because they are styled on the page with "-webkit-background-size: 30px 30px;" which Firefox doesn't see (and you won't see that style in Firefox's inspector, either – keep in mind that browsers OMIT all CSS they don't understand rather than leaving it in place as they do with HTML tags they don't understand).  

If you go into Safari on desktop (find a friend with a Macbook), turn on developer options there in preferences, change your user agent to iOS7 mobile, hit Gmail, log in, and inspect one of the stars you will see what I mean.  -webkit prefixed CSS is all over the place because that's all they google has really targeted on mobile since 2008. If Firefox interpreted "-webkit-background-size: 30px 30px;" and applied it as "background-size: 30px 30px;" or even "-moz-background-size: 30px 30px;" you would see gmail format correctly.

Comment 38

[Karl Dubost💡 :karlcow]

(In reply to misteranderson from comment #37)
> The next problem is primarily with the CSS. 

Yes. It's what I meant by it doesn't work.  
And as said, in comment #36, Google has been contacted.

Comment 39

[Aubrey Anderson]

amazing.

Comment 40

[Karl Dubost💡 :karlcow]

lowfi: https://mail.google.com/mail/u/0/x/unique_id/?f=1 (served to fxos, fxand, ie9 and ie10 mobile win, webos)
hifi: https://mail.google.com/mail/mu/mp/198/#tl/priority/^smartlabel_personal (served to chrome mobile and iOS, opera 15+ OPR mobile)


To note something quite interesting on my morning tests.

Safari on iOS is receiving different HIFI versions:

* The iOS8 Safari version is as broken as the chrome one on Firefox browser.
  Mozilla/5.0 (iPhone; CPU iPhone OS 8_0 like Mac OS X) AppleWebKit/538.34.9 (KHTML, like Gecko) Mobile/12A4265u

* The iOS3 Safari version is mostly working. Some little details with border images and stuff with webkit only properties:
  Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_0 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7A341 Safari/528.16

Comment 41

[Karl Dubost💡 :karlcow]

Attachment: gmail-firefox-android.jpg

In my quincentennial quest for the black art magic of UA detection, I think I got a new champion in the Camelot world of Google.

The only difference in between these two UA strings is… 3 characters "5.0"

Comment 42

[Karl Dubost💡 :karlcow]

Attachment: network-mozand5.0.png

And before we all think that we finally found the Saint Graal UA for inviting Google to give us the same thing. There are still issues.

When we tap on a message it never loads. It creates a request but it is 404.
Still encouraging that it's possible to get a decent layout given by Google.

Comment 43

[Chris Lord [:cwiiis]]

(In reply to Karl Dubost :karlcow from comment #41)
> Created attachment 8575120 [details]
> gmail-firefox-android.jpg
> 
> In my quincentennial quest for the black art magic of UA detection, I think
> I got a new champion in the Camelot world of Google.
> 
> The only difference in between these two UA strings is… 3 characters "5.0"

Interesting - I wonder if Android 4.0 would receive the same mark-up? (especially as we have very few b2g devices running 5.0)

Comment 45

[Karl Dubost💡 :karlcow]

todo: Worth retesting with 
* CSS whitelisting unprefixing Bug 1107378 
* and UA override https://hg.mozilla.org/mozilla-central/file/tip/b2g/app/ua-update.json.in

Comment 46

[Karl Dubost💡 :karlcow]

There is an issue currently with Gmail on Firefox Android. See 
https://webcompat.com/issues/1333

Comment 48

[Prahlad Yeri]

In case this helps anyone, it turned out in my case that the usual web-based Gmail setting was set to "classic mode" and not "standard mode". That was what causing the 90'ish display on the Firefox (Android) browser. Once I changed that setting from a desktop browser, the display was proper again. Just check out if that is not the case before burying your head inside this bug.

Comment 49

[Karl Dubost💡 :karlcow]

This is somehow fixed. I believe.

Comment 50

[Michal Stanke (Mozilla.cz) [:mstanke][:MikkCZ]]

Tried suggestions from comment #48 and cleaning cookies, cache and history, but still see the legacy version. Or does Google remember some per-device settings, so I need to clear them to?

Comment 51

[Mike Taylor [:miketaylr]]

Yes, not fixed for me as well.

Comment 52

[Karl Dubost💡 :karlcow]

Hmm weird I always test with a clean profile (out of the box), so I guess the issue is happening on the side of Gmail in your account preferences. Let me test this.

→ http --print hH https://mail.google.com/ 'User-Agent:Mozilla/5.0 (Android 4.4.4; Mobile; rv:44.0) Gecko/44.0 Firefox/44.0' 'Accept-Language:en-US,en;q=0.5'

HTTP/1.1 200 OK
Alt-Svc: quic=":443"; ma=604800; v="30,29,28,27,26,25"
Alternate-Protocol: 443:quic,p=1
Cache-Control: private, max-age=604800
Content-Length: 306
Content-Type: application/xhtml+xml; charset=ISO-8859-1
Date: Thu, 28 Jan 2016 00:57:39 GMT
Expires: Thu, 28 Jan 2016 00:57:39 GMT
Refresh: 0;URL=https://mail.google.com/mail/
Server: GSE
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block

Let's follow this Refresh header, it gives us:

https://accounts.google.com/ServiceLogin?service=mail&passive=true&continue=https://mail.google.com/mail/&ss=1&scc=1&ltmpl=ecobx&nui=5&btmpl=mobile&emr=1&osid=1

Let's request this, 
on the CLI I get a 200 OK.
on Opera/Blink Desktop (clean profile) with Firefox Android UA, I get a 200 OK with the classical login account.
But when I do this in Firefox Desktop (clean profile) with Firefox Android UA, I get a 302

HTTP/2.0 302 Found
Content-Type: text/html; charset=UTF-8
Strict-Transport-Security: max-age=10893354; includeSubDomains
X-Frame-Options: DENY
Location: https://mail.google.com/intl/en/mail/help/about.html
Content-Encoding: gzip
Date: Thu, 28 Jan 2016 01:06:22 GMT
Expires: Thu, 28 Jan 2016 01:06:22 GMT
Cache-Control: private, max-age=0
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Length: 189
Server: GSE
Set-Cookie: GAPS=1:z_xuvmTYhydEdiTPZvsQjPK7znywCA:95OOUO9Vl3buLI48;Path=/;Expires=Sat, 27-Jan-2018 01:06:22 GMT;Secure;HttpOnly;Priority=HIGH
Alternate-Protocol: 443:quic,p=1
Alt-Svc: quic=":443"; ma=604800; v="30,29,28,27,26,25"
X-Firefox-Spdy: h2

The only difference I can see is the headers for Accept-Language and the HTTP/2 negotiations.

I wonder if Mike deactivated UA override before testing? I did
https://hg.mozilla.org/mozilla-central/raw-file/tip/mobile/android/app/ua-update.json.in

On Firefox Android Clean Profile (Force Stop and Clear Data), I reached the account page. And I get the screen about the latest Gmail, HTML Gmail.

Take me to the latest Gmail does nothing indeed.

So my bad for closing too early.

On Firefox Desktop with Firefox Android UA, it goes to
https://mail.google.com/mail/mu/mp/198/#tl/priority/^smartlabel_personal with an interstitial for using Inbox

not sure how it's making a difference, in between all these devices and Configuration. Black magic.

The markup on the Android device for this screen is 

<div id="maia-main" role="main">
    <h1>Do you really want to use HTML Gmail?</h1>
    <p>You’re about to use a version of Gmail designed for slower connections and legacy browsers. To get all of Gmail’s features, including inbox categories, images, and quick actions, please use the latest version of Gmail (recommended).</p>
    <form action="https://mail.google.com/mail/u/0/x/xpnl023z3w65-/?a=uia" method="POST">
        <input name="at" value="AF6bupNaKJAQeNK3ksKUfYg-xisAbyB-mg" type="hidden">
        <p><a href="https://mail.google.com/mail/u/0" class="maia-button" style="margin-bottom: 5px; white-space: nowrap">Take me to latest Gmail</a>
            <input class="maia-button maia-button-secondary" value="I'd like to use HTML Gmail" type="submit">
        </p>
    </form>
</div>

When we tap https://mail.google.com/mail/u/0

We receive:

HTTP/2.0 302 Found
Content-Type: text/html; charset=UTF-8
Strict-Transport-Security: max-age=10886400; includeSubdomains
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Date: Thu, 28 Jan 2016 01:51:14 GMT
Location: https://mail.google.com/mail/u/0/x/11h8dssq3lm3a-/?f=1
Content-Encoding: gzip
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
Content-Length: 196
Server: GSE
Alternate-Protocol: 443:quic,p=1
Alt-Svc: quic=":443"; ma=604800; v="30,29,28,27,26,25"
X-Firefox-Spdy: h2


then

HTTP/2.0 302 Found
Content-Type: text/html; charset=UTF-8
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Date: Thu, 28 Jan 2016 01:51:14 GMT
Location: https://mail.google.com/mail/u/0/x/1latdswjk5gum-/?v=lui
Content-Encoding: gzip
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
Content-Length: 196
Server: GSE
Alternate-Protocol: 443:quic,p=1
Alt-Svc: quic=":443"; ma=604800; v="30,29,28,27,26,25"
X-Firefox-Spdy: h2

then

HTTP/2.0 200 OK
Content-Type: text/html; charset=UTF-8
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Date: Thu, 28 Jan 2016 01:51:15 GMT
Content-Encoding: gzip
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
Content-Length: 890
Server: GSE
Alternate-Protocol: 443:quic,p=1
Alt-Svc: quic=":443"; ma=604800; v="30,29,28,27,26,25"
X-Firefox-Spdy: h2

Which is basically the same page.

Oh wait… Even with general.useragent.site_specific_overrides set to false the Override is happening o_0
User-Agent: Mozilla/5.0 (Android; Mobile; rv:47.0) Gecko/47.0 Firefox/47.0


Could you confirm that Mike?

Comment 53

[Mike Taylor [:miketaylr]]

(In reply to Karl Dubost :karlcow from comment #52)
> Oh wait… Even with general.useragent.site_specific_overrides set to false
> the Override is happening o_0
> User-Agent: Mozilla/5.0 (Android; Mobile; rv:47.0) Gecko/47.0 Firefox/47.0
> 
> 
> Could you confirm that Mike?

I think you flipped off the wrong pref -- if you set general.useragent.updates.enabled to false the UA override will be disabled.

(After that, loading gmail is a lot more usable than it has been in the past -- just a few visual problems)

Comment 54

[Karl Dubost💡 :karlcow]

OK. 

Very good news. 
We can have a good experience on Firefox Android with just two simple modifications of the CSS.

I wrote about it.
http://www.otsukare.info/2016/03/17/fixing-broken-gmail

I'm recontacting Google.

Comment 55

[Mike Taylor [:miketaylr]]

Karl, do you think we should remove the override now? Or give Google some time to fix?

Comment 56

[Karl Dubost💡 :karlcow]

if we think that the button issue (It might create some issues of contrast for users) is less annoying than the simplified version,  we could make the switch and remove the UA override. The site is working well "__without__ webkit pref" so no issue for Release version of Firefox Android.

Comment 57

[Mike Taylor [:miketaylr]]

Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1231829#c6, let's wait a few more days to see if the Gmail border-image fixes solve our problems here (if they didn't just deploy them for Chrome UAs or something).

Comment 58

[Mike Taylor [:miketaylr]]

(Oh, https://bugs.chromium.org/p/chromium/issues/detail?id=559258#c56 says it might be a week or two for fixes to roll out)

Comment 59

[Karl Dubost💡 :karlcow]

Just a heads up 
This is fixed for Firefox on Android.

And 
https://bugzilla.mozilla.org/show_bug.cgi?id=1269049

Comment 61

[gianni]

I think that this bug should be reopened.
When I open gmail.com in firefox mobile, all I see is an outdated, stripped down version of the site. The same happens with google.com.
Obviously it all works perfectly in chrome.....

Comment 62

[Michal Stanke (Mozilla.cz) [:mstanke][:MikkCZ]]

(In reply to gianni from comment #61)
> I think that this bug should be reopened.
> When I open gmail.com in firefox mobile, all I see is an outdated, stripped
> down version of the site. The same happens with google.com.
> Obviously it all works perfectly in chrome.....

I was unable to reproduce this. How long do you see this issue? Are you able to reproduce it after clearing cookies, cache and other website related data stored in the browser? https://support.mozilla.org/en-US/kb/clear-your-browsing-history-and-other-personal-data

Comment 63

[gianni]

I've got Firefox 50.0.2 on android. I've tried to clear the cookies and ask the Firefox data.

The gmail site is clearly different, when viewed on chrome or in Firefox. For example in Firefox you don't see the formatting of the text, and when you forward a message the images and the hyperlinks disappear.

Also there is a very big difference on google. In chrome you see many different search options (images news etc) while on firefox you see only the images options, and for example you can't search by date.

Comment 64

[Mike Taylor [:miketaylr]]

That's strange. Gianni, can you provide your mobile User Agent string? You can find it at echo.opera.com. It will look something like "User-Agent:	Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Firefox/52.0" (if you were using Desktop).

Comment 65

[gianni]

Bug is still valid. One of the worse thing, is that when I forward a message from a gmail tab opened in firefox mobile, the html content gets stripped. url and images disappear, making the email unusable.

Comment 66

[gianni]

I would like to ask you to open a mail in the gmail.com website, and try to edit or forward it. 
What happens to me is that html gets messed up: hyperlinks and formatting are removed, and the same happens to embedded images.

Comment 67

[Emilio Cobos Álvarez (:emilio)]

Fwiw I arrived here tracking down why Google sent Firefox for android a different search results page than to any other UA.

My UA is:

 * Mozilla/5.0 (Android 7.1.1; Mobile; rv:54.0) Gecko/54.0 Firefox/54.0 

(which is nightly, but also repros on release).

Changing the UA to Chrome's or Opera's makes Google send a more fancy page, but it's even worse since they seem to just blacklist Firefox. A UA like:

 * Mozilla/5.0 (Linux; Android 7.1.1;

(Literally, I didn't miss anything, that's the UA I tested)

Still sends the nicer page :(. Worth opening a new bug for this one?

Comment 68

[Karl Dubost💡 :karlcow]

Emilio, This bug is about Gmail. :)

The bug (you can follow if you wish) about Google search is Bug 975444
Google has already been contacted.

Comment 69

[Emilio Cobos Álvarez (:emilio)]

(In reply to Karl Dubost :karlcow from comment #68)
> Emilio, This bug is about Gmail. :)
> 
> The bug (you can follow if you wish) about Google search is Bug 975444
> Google has already been contacted.

Ouch, my bugsearch-foo is not good enough apparently, I missed that one, thanks :)

Comment 70

[gianni]

Still - in gmail.com - it doesn't show the tabs

google+, gmail, calendar, web 

otherwise the gmail.com has improved, but still it doesn't look the same as in chrome