css.properties.font-synthesis - font-synthesis: none doesn't work on Chrome
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
What type of issue is this?
Incorrect support data
What information was incorrect, unhelpful, or incomplete?
Using font-synthesis: none; should prevent the browser from generating faux-italic fonts, but this doesn't work in Chromium.
It works fine in Safari and Firefox
What browsers does this problem apply to, if applicable?
Chromium (Chrome, Edge 79+, Opera, Samsung Internet)
What did you expect to see?
Regular fonts, not synthesised faux-italic ones.
Did you test this? If so, how?
Yes. Edit the css on the title on https://fonts.google.com/knowledge/glossary/faux_fake_pseudo_synthesized which doesn't have italic glyphs.
Safari and Firefox will honor the following, while Chromium will not.
{
font-style: italic;
font-synthesis: none;
}
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
https://bugs.chromium.org/p/chromium/issues/detail?id=1416834&q=font-synthesis&can=2
Do you have anything more you want to share?
No response
MDN URL
https://developer.mozilla.org/en-US/docs/Web/CSS/font-synthesis
MDN metadata
MDN page report details
- Query:
css.properties.font-synthesis - Report started: 2023-02-16T11:20:25.693Z
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the css.properties.font-synthesis entry and compare its Chromium compatibility data with the reproduction on the Google Fonts page. Review Chromium bug 1416834 and the linked MDN page for the expected behavior. Done means the compatibility data accurately reflects Chromium's handling of font-synthesis: none.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100