commit | 6df58d58e667f19490acc1c51095aaf08842bea7 | [log] [tgz] |
---|---|---|
author | Dominik Röttsches <drott@chromium.org> | Mon Jun 17 16:56:49 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 17 16:56:49 2024 |
tree | 508176f6247d273b7f74791dcecca9f708410c81 | |
parent | 654bd4d577ccf08b9291b1a7905ee467396ea346 [diff] |
[Fontations] Enable Fontations for selected formats Enable the Fontations font back-end for less commonly used formats, as announced in [1] and [2]. As this includes switching to Fontations' COLRv1 implementation which has higher internal precision for gradient computations, this also addresses issue 40278815. Add a test to cover synthetic bold and italic for the CFF test font. Add baselines with slightly changed COLRv1 renderings. Add inspector-protocol/layout-fonts baselines that show the (Fontations) suffix in font name. We leave that in for being able to identify whether Fontations is active in bug reports and remove this suffix when the migration is complete, see [3]. [1] https://groups.google.com/a/chromium.org/g/blink-dev/c/4xUt73fxCrU [2] https://issues.chromium.org/343584524 [3] https://issues.skia.org/307906051 Bug: 343584524, 40278815 Cq-Include-Trybots: luci.chromium.try:linux-blink-rel,win11-blink-rel,mac14-blink-rel,win10.20h2-blink-rel Change-Id: Ic2ff84eaa6630ca36dbb52328f4dcc005f01d36b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5614312 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Ben Wagner <bungeman@google.com> Commit-Queue: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/main@{#1315932}
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.