Use correct Surface::Type for font lookups by unique name only
Currently, such lookups are accidentally recorded under
kLocalFontLookupByUniqueOrFamilyName due to a typo. This affects the
metrics recording for the identifiability study
(cherry picked from commit 7a5a9f5996cc2aaec80705507d561fa439d9c46f)
Bug: 1136921
Change-Id: Ibf4a28a6edfabff0a570bd35c09686b5b020957d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2463702
Reviewed-by: Asanka Herath <[email protected]>
Reviewed-by: Dominik Röttsches <[email protected]>
Commit-Queue: Alex Turner <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#816675}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485673
Commit-Queue: Asanka Herath <[email protected]>
Cr-Commit-Position: refs/branch-heads/4280@{#513}
Cr-Branched-From: ea420fb963f9658c9969b6513c56b8f47efa1a2a-refs/heads/master@{#812852}
diff --git a/third_party/blink/renderer/platform/fonts/font_matching_metrics.cc b/third_party/blink/renderer/platform/fonts/font_matching_metrics.cc
index e3168ad..efce7b3 100644
--- a/third_party/blink/renderer/platform/fonts/font_matching_metrics.cc
+++ b/third_party/blink/renderer/platform/fonts/font_matching_metrics.cc
@@ -254,7 +254,7 @@
{&font_lookups_by_unique_or_family_name_,
IdentifiableSurface::Type::kLocalFontLookupByUniqueOrFamilyName},
{&font_lookups_by_unique_name_only_,
- IdentifiableSurface::Type::kLocalFontLookupByUniqueOrFamilyName},
+ IdentifiableSurface::Type::kLocalFontLookupByUniqueNameOnly},
{&font_lookups_by_fallback_character_,
IdentifiableSurface::Type::kLocalFontLookupByFallbackCharacter},
{&font_lookups_as_last_resort_,
