Expose delivery type in PerformanceResourceTiming. about resource-timing HOT 7 CLOSED

Right now, consuming a preloaded resource doesn't create an entry. Modifying that would require some discussion, which started in #303. IIUC, your proposal here matched @noamr's "separate entry" proposal. Is that correct?

from resource-timing.

Yes, I propose that consuming a preloaded resource create a separate entry, like Noam's separate entry proposal.

from resource-timing.

@yoavweiss @noamr Trying to unblock these two issues; wdyt?

The delta to this specification is fairly small: https://github.com/w3c/resource-timing/compare/gh-pages...jeremyroman:resource-timing:resource-timing-prefetch?expand=1

from resource-timing.

Yes I think we should have separate entries for each fetch and separate them by something like this proposal. Not sure how to advance towards a consensus on #303 though.

from resource-timing.

I defer to you and Yoav about what the right process is within Web Perf WG (CONTRIBUTING.md seems to say "enough support" after review by WG participants), but it seems like a proposal like this one would:

• make it easy for authors/RUM libraries to filter out the preload consume records if they wanted to
• be consistent with how cached resources work, give flexibility moving forward about whether/how to expose the timing of the underlying navigational prefetch itself (whether it's shown to the referring page, the destination page, neither or both), and
• address the problem in w3c/navigation-timing#163 (performance.getEntriesByType('navigation')[0].deliveryType === 'navigational-prefetch')

My preferred way of making forward progress is to make a concrete proposal (this one, adapted from the linked comment), solicit feedback (maybe this needs to go to a WPWG F2F? unsure about process) and then write tests (per CONTRIBUTING.md) and try to merge it.

from resource-timing.

Blocked on #303

from resource-timing.

Since I was not able to advance #303 recently, I propose this goes ahead, and we coordinate that it has #303 in mind to keep consistency in naming and meanings.

from resource-timing.