Bug 1667499 [wpt PR 25799] - Reland "FontAccess: Sort fonts in lexicographical order...
commit3d34d15b10c3393440b88a23a0caf51ff1523121
authorOlivier Yiptong <oyiptong@chromium.org>
Tue, 6 Oct 2020 14:18:21 +0000 (6 14:18 +0000)
committermoz-wptsync-bot <wptsync@mozilla.com>
Thu, 8 Oct 2020 10:18:15 +0000 (8 10:18 +0000)
treed2bbc883fb519038f96ddd2b240976631d130247
parentf58d427901faf90f0e9a8a2e9c89fade7d019c93
Bug 1667499 [wpt PR 25799] - Reland "FontAccess: Sort fonts in lexicographical order", a=testonly

Automatic update from web-platform-tests
Reland "FontAccess: Sort fonts in lexicographical order"

This is a reland of 404b7cc426e259c11276d673630c9f094628259f

The original CL failed some tests because the code assumes that
platform-specific APIs called returned unique data. This was a false
assumption.

This reland follows another CL: https://crrev.com/c/2438875, which
ensures that fonts are not duplicated.

Original change's description:
> FontAccess: Sort fonts in lexicographical order
>
> This change ensures fonts are sorted before being cached. This change is
> due to a concern about fingerprinting:
> https://github.com/w3ctag/design-reviews/issues/399#issuecomment-530679815
>
> This change ensures that fonts are sorted in lexicographical order.
>
> Bug: 1043306
> Change-Id: Ia3acf2a45cb473124df4e489683bdc7bac15dde4
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2427040
> Commit-Queue: Olivier Yiptong <oyiptong@chromium.org>
> Reviewed-by: Joshua Bell <jsbell@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#810519}

Bug: 1043306
Change-Id: Ic3d70744661a838d82349c017a1cb0e8c23a3654
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2432815
Commit-Queue: Olivier Yiptong <oyiptong@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812965}

--

wpt-commits: cd769106a3ea014cc1b0f8a90bfeac8e8d9a8ab7
wpt-pr: 25799
testing/web-platform/tests/font-access/resources/window-tests-enumeration.js