Fonts initiator is not properly attributed to stylesheet

[patrickhulce]

Provide the steps to reproduce

1. Run LH on http://localhost:10200/preload.html

What is the current behavior?

In "Critical Request Chains" audit, observe that the font /perf/lobster-v20-latin-regular.woff2 is not nested underneath the /perf/preload_style.css file that initiates it.

What is the expected behavior?

The font /perf/lobster-v20-latin-regular.woff2 is nested underneath the /perf/preload_style.css file that initiates it.

This has significant consequences for Lantern accuracy as well.

Environment Information

• Affected Channels: CLI
• Lighthouse version: 4.0.0-beta

Related issues
#6417

[patrickhulce]

I'll try and track down the last Chrome version where it worked.

It never did? 😕I went as far back as m61 (~mid 2017), but I couldn't get the stylesheet to show up as the initiator in DevTools. I'm convinced this used to work though, or there's no way we could've been recommending slick.woff in the first place for the parent bug to have been filed (#6417)!

In our smoke test page, the initiator gets falsely attributed to the line of the document that adds the script tag and if you comment that line out, the initiator just drops to Other

[paulirish]

The other piece here is that if script is forcing a reflow, then the initiator will point to that, rather than the stylesheet reference of that font. But if a style recalc was done async (not forced) then the initiator should be correct.

All that said, there are some places where the initiator data is wrong, so it could be that case, as well. https://bugs.chromium.org/p/chromium/issues/detail?id=570298

[andydavies]

I think you might be looking for this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=570298

There's another issue related to aligning the initiator with Resource Timing definition that's marked as won't fix too - https://bugs.chromium.org/p/chromium/issues/detail?id=599648