commit | c23f99b74b4f738fe1f5a3e04cca8c9d2f17aaed | [log] [tgz] |
---|---|---|
author | ChangSeok Oh <changseok.oh@bytedance.com> | Wed Oct 18 18:45:40 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 18 18:45:40 2023 |
tree | 6f5b8cdbdec5b77cb525dbf2862fe3aed7ab3953 | |
parent | af07921fab7fe0b3efd22fffd8e1582ed5d78235 [diff] |
Make document.fonts.check() in conformance with the updated spec. The document.fonts.check() neither behaves as the current spec document describes [1] nor other rendering engines behave. First, the FontFaceSet::check() should return true for non-existent fonts [2]. Second, the check method should not reveal any platform fallback font existence. Third, the existing implementation does not follow the updated checking steps (e.g., checking the range intersection with the given text is inefficient and erroneous, where all found font faces support the same character set). So, this CL re-implements document.fonts.check(), conforming to the standard and other engines' behaviors. [1] https://www.w3.org/TR/css-font-loading/#font-face-set-check [2] https://github.com/w3c/csswg-drafts/issues/5744 Test: external/wpt/css/css-fonts/fallback-url-to-local.html fast/css/fontfaceset-check-platform-fonts.html Bug: 1416842 Change-Id: I246792ec99190db5a8b59f653bc19cfbb7850d3e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4913179 Commit-Queue: ChangSeok Oh <changseok.oh@bytedance.com> Reviewed-by: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/main@{#1211649}
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.