Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Emojis don't display on browser without COLR and without SBIX support #10351

Closed
non-Jedi opened this issue Jul 16, 2019 · 8 comments
Closed

Emojis don't display on browser without COLR and without SBIX support #10351

non-Jedi opened this issue Jul 16, 2019 · 8 comments
Labels
A-Emoji T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter

Comments

@non-Jedi
Copy link

non-Jedi commented Jul 16, 2019

Description

riot-emoji-boxes

Fallback to Noto Color Emoji is no longer working on browsers that
have neither COLR nor SBIX support. If I add the following to my
user-style-sheet, I can see some emoji, but the emoji within the
reaction picker still don't display.

.mx_scrollbar_overlay_noautohide {
    font-family: Nunito, 'Noto Emoji', Sans-Serif ! important;
}

Steps to reproduce

qutebrowser-chroma-check

Load Riot web in a browser without COLR and without SBIX support on
Linux with Noto Color Emoji installed. Navigate to page containing emoji.

Version information

  • Platform: web

For the web app:

  • Browser: qutebrowser v1.6.3 ( QtWebEngine (Chromium 73.0.3683.105))
  • OS: Void Linux
  • URL: riot.im/develop
@non-Jedi
Copy link
Author

As an additional note, if I load a user-stylesheet while Riot is already active, the emoji in the reaction picker are displayed correctly as well as everything else. It's only if the user stylesheet is loaded before Riot that the reaction picker emoji are special snowflakes.

@turt2live
Copy link
Member

Related: #10296

@non-Jedi can we get a rageshake for this? There's some troubleshooting logs specifically for this problem which may be of use to the person who looks into this.

@non-Jedi
Copy link
Author

done

@jryans
Copy link
Collaborator

jryans commented Jul 19, 2019

Thanks for the additional details. What are the results from the ChromaCheck page if you try regular Firefox or Chrome (as opposed to qutebrowser)?

@jryans jryans added defect A-Emoji X-Needs-Info This issue is blocked awaiting information from the reporter labels Jul 19, 2019
@non-Jedi
Copy link
Author

Firefox supports SVG-in-Opentype only and Chromium supports all but SVG-in-Opentype. Qt-Webengine uses an older version of chromium internally though.

@ara4n
Copy link
Member

ara4n commented Jul 19, 2019

this just sounds like the fallback to noto has got lost somewhere...

@globau
Copy link

globau commented Jan 23, 2020

This is caused by the Twemoji font – removing it from the font-family declaration on the body element resolves this issue.

@turt2live
Copy link
Member

Presuming fixed by the new font family.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Emoji T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter
Projects
None yet
Development

No branches or pull requests

5 participants