User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.55 Safari/537.36

Steps to reproduce:

See WPT: https://github.com/web-platform-tests/wpt/pull/31539

Actual results:

Fonts and styles reuse the preloaded resource even if the cors attributes don't match (fonts are to be loaded as anonymous-cors)

Expected results:

Preloaded resources (<link rel=preload />) should be reused by their consumer based on their resource types and CORS-related attributes.

The Bugbug bot thinks this bug should belong to the 'Core::Layout: Text and Fonts' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

The severity field is not set for this bug.
:alaskanemily, could you have a look please?

For more information, please visit auto_nag documentation.

(In reply to Noam Rosenthal from comment #0)

See WPT: https://github.com/web-platform-tests/wpt/pull/31539

Looks like this WPT landed and lives at:
https://wpt.fyi/results/preload/preload-resource-match.https.html

I assume the bug report here is about our various subtest-failures in that WPT test (though it's worth noting that nearly all of our subtest-failures also have some other browser failing the same subtest).

In any case: I'm tentatively reclassifying under Networking for triage/investigation (looks like preload bugs are mostly bucketed there, and bugbot mistakenly classified this under Layout:Text/Fonts due to the fact that one of the loaded resources here is a font).

(In reply to Daniel Holbert [:dholbert] from comment #3)

(In reply to Noam Rosenthal from comment #0)

See WPT: https://github.com/web-platform-tests/wpt/pull/31539

Looks like this WPT landed and lives at:
https://wpt.fyi/results/preload/preload-resource-match.https.html

I assume the bug report here is about our various subtest-failures in that WPT test (though it's worth noting that nearly all of our subtest-failures also have some other browser failing the same subtest).

Yes. It's part of a web performance WG effort to align the different browsers on preload behavior which was previously underspecified and differs between browsers. as part of that work we've specified the missing pieces and added corresponding WPTs and opened issue reports for the different browser engines.

I went through this again and this could be an issue with the test rather than a problem in Firefox.
https://github.com/web-platform-tests/wpt/pull/32831

It looks like you are right. Font problems are solved using Unicode generators such as https://exoticfonts.com/superscript-generator/