Chrome Incorrectly Selects Fallback Font When src:local("")
When the src: local(..) inside @font-face is specified as empty
(@font-face { src: local(""); }), Chrome incorrectly selects a fallback
font. Ideally, it should fallback on the standard font. The issue arises
from Chrome's font matching method, which allows it to find a font with
a blank src path, leading to the fallback on an incorrect font. Other
browsers, like Safari and Firefox, render the default font in case of an
empty src
Bug: 342067852
Change-Id: Id2ffbcaf63812bef2b8f71b90e64cc05b8f79855
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6344210
Reviewed-by: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Kurt Catti-Schmidt <kschmi@microsoft.com>
Commit-Queue: Gaurav Kumar <gauravkum@microsoft.com>
Reviewed-by: Vinay Singh <vinaysingh@microsoft.com>
Reviewed-by: Dileep Maurya <dileepmaurya@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1436963}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.