Unable to load emoji's icons in settings panel.

[wtfzambo]

Edit by @rsese to add the issue template

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

Installed some packages (essentially hydrogen and whatever revolves around it), then after a while I noticed that the emojis were missing, and in place of them I'd just see the generic image icon and the name of the emoji (screenshot attached).

Steps to Reproduce

1. Start Atom
2. Open Settings View
3. Click Install
4. Search for "hydrogen launcher"
5. Click on the hydrogen-launcher result to bring up the package view

Expected behavior:

Expect to see the 🚀 emoji in the README.

Actual behavior:

See a broken image for the emoji.

On Windows 10:

On macOS 10.14.6 where the emoji shows up ok:

Reproduces how often:

100%

Versions

Reproduced on Windows 10 but not on macOS 10.14.6.

$ atom -v
Atom    : 1.40.1
Electron: 3.1.10
Chrome  : 66.0.3359.181
Node    : 10.2.0

Additional Information

n/a

---

Long story short, I restarted using atom yesterday for python development.

Installed some packages (essentially hydrogen and whatever revolves around it), then after a while I noticed that the emojis were missing, and in place of them I'd just see the generic image icon and the name of the emoji (screenshot attached).

Just to make it clear: they were present at the beginning, and only went missing after a while.

So I started atom in safe mode via atom --safe, but to no avail. Tried to search a solution online but wasn't able to find anything related to my problem.

I know it's a stupid problem but it triggers my autism so much, any info or help is much appreciated.

pic related:

[rsese]

Thanks for the report @wtfzambo! I thought this has been brought up before but I couldn't an existing issue so maybe I'm mis-remembering.

Also, for future issues please use the issue template or your issues may be closed. The template information and format are super helpful for us when triaging issues; for example, it's not clear what operating system you're running, what version of Atom, etc. In this case I went ahead and added the template information since I can reproduce on Windows 10 (though it didn't reproduce on macOS 10.14.6 for me).

[wtfzambo]

Hi @rsese!

Related to the issue, the weird part is that when I first fired up atom yesterday the issue wasn't present. It started happening later on. Btw yes I'm on win10 and using the latest stable version of atom.

Also thanks for fixing my post for me and sorry for not using the template, I honestly didn't pay attention to the fact that it was actually suggested in the input field already, I just went ahead and cleared everything D:

[rsese]

Also noting that this is the case with other emoji besides 🚀, using https://atom.io/themes/alice-gh-ui for example (see 🍔 and 🍟 towards the bottom of the image):

But it does look like the emoji itself shows up fine (you can see in the screenshot there), it's the emoji that uses the emoji codes that aren't working - so :rocket: is what's showing as the broken image in this example. The package mentioned in the OP also uses :rocket: rather than the emoji itself: https://github.com/lgeiger/hydrogen-launcher/blob/aeee89b521cd3f391854007595287debc10cdd55/README.md.

[wtfzambo]

@rsese Alright, so is there something I should be doing on my end to fix the issue?

[rsese]

No nothing to do on you end, there's no setting to change that would make the emoji render and no workaround for the problem. At the moment, it seems like something that would need to be fixed - with all the work on the team's plate right now I think it's unlikely to be prioritized on our end but we're always open to reviewing well-written pull requests from the community.

[wtfzambo]

I'm too much of a beginner in these kind of stuff to do a pull request yet, but thanks for helping and all 👍