1342697 - When adding emoji in Gmail, emoji icons fail to display in Firefox

Status: RESOLVED WORKSFORME

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

Description

[agoodanswer]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20170125094131

Steps to reproduce:

Recently -- within the past few weeks -- I haven noticed that the emoji icons that are available in Gmail no longer display.  Emoji that are already in an email show up, but in the drop-down menu the icons for emoji do not display, although the emoji themselves are loaded and can blindly be clicked on/selected.


Actual results:

I have tried Gmail in Firefox across multiple operating systems, I have updated drivers, turned off plugins, etc.  I cannot get the emoji icons in the Gmail drop-down menu to display.

On the other hand, if I load Opera in any OS, the Gmail emoji in the drop-down show up as expected.


Expected results:

I don't know what's broken, but it's consistent only to Firefox.  I am currently running 51.0.1.

Comment 1

[YF (Yang)]

Bug 591822 comment 50.

Comment 2

[Masatoshi Kimura [:emk]]

Works for me using Nightly on Windows 10 with or without HWA, with or without e10s.

(In reply to agoodanswer from comment #0)
> User Agent: Mozilla/5.0 (Windows NT 5.1; rv:51.0) Gecko/20100101 Firefox/51.0

Is this bug reproducible on newer versions of Windows? If not, this bug is very likely to be WONTFIX.

> Product: Firefox → Tech Evangelism

I don't think we should force Google to workaround our (soon) unsupported configurations.

Comment 3

[YF (Yang)]

(In reply to Masatoshi Kimura [:emk] from comment #2)
> Works for me using Nightly on Windows 10 with or without HWA, with or
> without e10s.

Using gfx.content.azure.backends to "cairo". It is necessary for MacType users, at least.

> (In reply to agoodanswer from comment #0)
> > User Agent: Mozilla/5.0 (Windows NT 5.1; rv:51.0) Gecko/20100101 Firefox/51.0
> 
> Is this bug reproducible on newer versions of Windows? If not, this bug is
> very likely to be WONTFIX.

This issue can be reproduced in 54.0a1 (2017-02-27) (32-bit) on Win10.

> > Product: Firefox → Tech Evangelism
> 
> I don't think we should force Google to workaround our (soon) unsupported
> configurations.

As it is an external change to raise the issue now. It worked once.

Comment 4

[Masatoshi Kimura [:emk]]

(In reply to YF (Yang) from comment #3)
> (In reply to Masatoshi Kimura [:emk] from comment #2)
> > Works for me using Nightly on Windows 10 with or without HWA, with or
> > without e10s.
> 
> Using gfx.content.azure.backends to "cairo". It is necessary for MacType
> users, at least.

It is exactly an unsupported configuration. Also, it is very unlikely that our very old cairo copy will get a fix.

> > (In reply to agoodanswer from comment #0)
> > > User Agent: Mozilla/5.0 (Windows NT 5.1; rv:51.0) Gecko/20100101 Firefox/51.0
> > 
> > Is this bug reproducible on newer versions of Windows? If not, this bug is
> > very likely to be WONTFIX.
> 
> This issue can be reproduced in 54.0a1 (2017-02-27) (32-bit) on Win10.

With the cairo backend? It is a bit misleading to omit important information.

> > > Product: Firefox → Tech Evangelism
> > 
> > I don't think we should force Google to workaround our (soon) unsupported
> > configurations.
> 
> As it is an external change to raise the issue now. It worked once.

Every site used to work with IE6.

Comment 5

[YF (Yang)]

(In reply to Masatoshi Kimura [:emk] from comment #4)
> (In reply to YF (Yang) from comment #3)
> > (In reply to Masatoshi Kimura [:emk] from comment #2)
> > > Works for me using Nightly on Windows 10 with or without HWA, with or
> > > without e10s.
> > 
> > Using gfx.content.azure.backends to "cairo". It is necessary for MacType
> > users, at least.
> 
> It is exactly an unsupported configuration. Also, it is very unlikely that
> our very old cairo copy will get a fix.

This is regrettable. For MacType users, using DirectX/skia as render may be difficult to accept.

> > > (In reply to agoodanswer from comment #0)
> > > > User Agent: Mozilla/5.0 (Windows NT 5.1; rv:51.0) Gecko/20100101 Firefox/51.0
> > > 
> > > Is this bug reproducible on newer versions of Windows? If not, this bug is
> > > very likely to be WONTFIX.
> > 
> > This issue can be reproduced in 54.0a1 (2017-02-27) (32-bit) on Win10.
> 
> With the cairo backend? It is a bit misleading to omit important information.

Yes. It looks work fine for default configuration (direct2d1.1 or skia when hardware acceleration option is disabled). I don't know the configuration of the reporter.

> > > > Product: Firefox → Tech Evangelism
> > > 
> > > I don't think we should force Google to workaround our (soon) unsupported
> > > configurations.
> > 
> > As it is an external change to raise the issue now. It worked once.
> 
> Every site used to work with IE6.

I don't understand what you mean. Just explain for moving to here. If Google intends to make an workaround to serve for a handful of users. even we don't inform them, can also be archived here.


p.s. It can also be reproduced if gfx.content.azure.backends to direct2d1.1,cairo (backout bug 1007702) and gfx.direct2d.disabled to true, This is the situation before bug 1007702.

Comment 6

[Masatoshi Kimura [:emk]]

Remove dependency because bug 591822 will not fix this.

Comment 7

[Oana Arbuzov [:oanaarbuzov]]

I can't reproduce the issue on my side on Windows 10 with or without the config changes ('gfx.content.azure.backends' to 'direct2d1.1,cairo' and 'gfx.direct2d.disabled' to 'true').
https://prnt.sc/vkv5wk

Tested with:
Browser / Version: Firefox Nightly 85.0a1 (2020-11-16)
Operating System: Windows 10 Pro

Cipri can you reproduce it on your Mac?

Comment 8

[Ciprian Ciocan [:ciprian]]

The emoticons are displayed for me, too.

https://prnt.sc/vlcnks

Tested with:
Browser / Version: Firefox Nightly 85.0a1 (2020-11-17)
Operating System: macOS 10.15.6

Comment 9

[Oana Arbuzov [:oanaarbuzov]]

Thank you Cipri, I'll close the issue.

agoodanswer if you are able to still reproduce, feel free to reopen.