-
Notifications
You must be signed in to change notification settings - Fork 75
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
Chrome emoji functionality not restored after uninstalling. #137
Comments
🤔 That's strange, the uninstall script just reinstalls the original fonts. Confirm they are on your system? Check the script here: https://github.com/13rac1/twemoji-color-font/blob/85d28019f7ddb400be1a729ba9cbf53d2e1e2589/windows/uninstall.cmd |
I can find a font called Segoe in my C:/Windows/Fonts folder. My emoji keyboard from shortcut edit: the emoji are working fine on Firefox, seems to be a Chrome issue. I'd like to know if it's possible to make it work in Chrome again. |
I'm having the same issue, only with the Edge browser. I ran the uninstaller and rebooted twice. The emojis on the browser are still in B&W. I noticed it only seems to happen on certain sites. It happens on this one and archiveofourown.org. I can also see the emojis on this page, though exhale is a cloud rather than a face. https://emojipedia.org/smileys Things like melting or smiling with tear are missing, but the others show up. Not sure what's going on. |
Okay. I figured it out for me. I had the wrong font chosen on the browser. I had OpenMoji Color instead of Segoe UI Emoji. User error on my part. |
How did you change the font on the browser? I'm encountering this issue as well after uninstall. |
same, uninstall it. but icon also black white color |
I tried to uninstall since I am using Chrome mainly now and would like not to have the fallback emoji.
However the uninstall script did not restore the emoji functionality of Chrome.
How do I restore it? Is it possible to make it a part of the uninstall script?
Using Windows 10. Font version 14.0.2
Steps:
The text was updated successfully, but these errors were encountered: