a7cdc4b222
In [1] a Skia flag was introduced to switch to Fontations for system fonts. Enable this flag in skia/fontations_feature.cc and rebaseline the world: - ash tests work with revision_numbers that need to be increased for Skia gold to allow them to be changed. - web tests rebaselines The rebaselines are due to subtle differences in text antiliasing and have been inspected for regressions. We already rolled out Fontations for web fonts, which gives us confidence the rendering output is not disrupted. [1] https://chromium-review.googlesource.com/c/chromium/src/+/6286047 Design doc: go/rust-fontstack-chrome (internal) Fixed: chromium:346918516 Cq-Include-Trybots: luci.chromium.try:linux-blink-rel Change-Id: I2d64a6faba820b556a6ce789456e38ecefe4b7f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6169919 Reviewed-by: Rick Byers <rbyers@chromium.org> Owners-Override: Rick Byers <rbyers@chromium.org> Reviewed-by: Mitsuru Oshima <oshima@chromium.org> Commit-Queue: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/main@{#1430666}
In-Session User Authentication Dialog
This Ash dialog is for authenticating the user during a user session. The primary use case is WebAuthn, where a platform daemon (u2fd) receives an authentication request from the Chrome browser, and needs to initiate a user authentication dialog which could involve fingerprint, PIN and password. More authentication methods, such as SmartLock and smart cards, might be added in the future.
This dialog is designed to be reused by other projects that need to trigger in-session user authentication from ChromeOS, such as authenticating for ARC apps.
This dialog is controlled by ash::AuthDialogController. When the user provides a credential, the controller talks to cryptohome via ash::AuthPerformer for authentication.