We've got a bunch of w3c-submitted reftests that use a *local copy* of the "Ahem" font: https://dxr.mozilla.org/mozilla-central/source/testing/web-platform/tests/css/vendor-imports/mozilla/mozilla-central-reftests/flexbox/support/Ahem.ttf https://dxr.mozilla.org/mozilla-central/source/testing/web-platform/tests/css/vendor-imports/mozilla/mozilla-central-reftests/ruby/support/Ahem.ttf https://dxr.mozilla.org/mozilla-central/source/testing/web-platform/tests/css/vendor-imports/mozilla/mozilla-central-reftests/text3/support/Ahem.ttf https://dxr.mozilla.org/mozilla-central/source/testing/web-platform/tests/css/vendor-imports/mozilla/mozilla-central-reftests/variables/support/Ahem.ttf We should perhaps move away from doing this? These submissions end up in WPT, which I think provides the Ahem font automatically. ("Aside from the Ahem font, fonts cannot be relied on to be .... installed" http://web-platform-tests.org/writing-tests/general-guidelines.html ) I suspect that in our own (non-WPT) reftest harness, Ahem cannot be relied on to be installed, which is why we're needing to provide it here. But as a result, we're adding clutter to our WPT-submitted tests.
er, sorry - I just noticed the links in comment 0 are all from the WPT "vendor-imports" directory. The more direct source of these files (where we'd want to make changes) is here & in the neighboring HTML files that use them: https://dxr.mozilla.org/mozilla-central/source/layout/reftests/w3c-css/submitted/flexbox/support/Ahem.ttf https://dxr.mozilla.org/mozilla-central/source/layout/reftests/w3c-css/submitted/ruby/support/Ahem.ttf https://dxr.mozilla.org/mozilla-central/source/layout/reftests/w3c-css/submitted/text3/support/Ahem.ttf https://dxr.mozilla.org/mozilla-central/source/layout/reftests/w3c-css/submitted/variables/support/Ahem.ttf
There has been quite a bit of discussion around how Ahem should be handled. I think dbaron or someone once raised that we should probably change all ahem flag to just use @font-face instead, since that flag exists simply because there wasn't such feature at that days. But that's probably not very helpful given the current situation.
You need to log in before you can comment on or make changes to this bug.