-
Notifications
You must be signed in to change notification settings - Fork 715
[css-fonts] Drop the emoji font-family #9359
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
Comments
As far as I can tell, this was introduced in response to https://lists.w3.org/Archives/Public/www-style/2014Aug/0323.html, which seems to confirm that the motivation was indeed the same problem that is now better solved with |
Precisely:
So yes, it might have been an okay idea in 2014 but is entirely redundant now. |
Indeed, the discussion that led to |
I am in favor of removing it and agree with @frivoal's comment above. |
Proposed async resolution: Remove the |
The CSSWG will automatically accept this resolution one week from now if no objections are raised here. Anyone can add an emoji to this comment to express support. If you do not support this resolution, please add a new comment. Proposed Resolution: Remove the |
RESOLVED: Remove the |
Sorry to comment on a closed issue, but I am under the impression that UPDATE: apparently Chromium is working on fixing the issue I mentioned so that |
The CSS Working Group just discussed The full IRC log of that discussion |
I may be missing something, but I think the
emoji
font family serves no useful purpose, and does not have well defined behavior, so we should drop it.The only thing I think it could reasonably be used for is better served by the
font-variant-emoji
property: for the few characters that can ambiguously have an emoji rendering, or a symbol rendering, this lets you pick how they are rendered.Other than this choice of variant, which is better defined in and better suited to
font-variant-emoji
property, it seems to me that an emoji font-family doesn't make sense.Am I missing something? If no, we should drop that family.
cc @svgeesus
The text was updated successfully, but these errors were encountered: