Open Elchi3 opened 1 year ago
If so, would it be a good idea to include the following types in the Resource Timing note?
body
early-hint
(orearly-hints
, the Fetch spec and Chrome seem to diverge here.)embed
font
link
object
ping
@noamr - are all these types valid initiator type values? I'm somewhat surprised by some of them (e.g. "body" & "font")
If so, would it be a good idea to include the following types in the Resource Timing note?
body
early-hint
(orearly-hints
, the Fetch spec and Chrome seem to diverge here.)
embed
font
link
object
ping
@noamr - are all these types valid initiator type values? I'm somewhat surprised by some of them (e.g. "body" & "font")
Font face="..." Though I have to make sure...
Body background="..." For sure
As part of a project to update MDN's Performance API docs (https://github.com/openwebdocs/project/issues/62), I updated https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming/initiatorType.
The Resource Timing spec contains a non-normative note listing
initiatorType
types: https://w3c.github.io/resource-timing/#dom-performanceresourcetiming-initiatortype. I believe a normative list of types is in the Fetch spec: https://fetch.spec.whatwg.org/#request-initiator-type. Is that correct?If so, would it be a good idea to include the following types in the Resource Timing note?
body
early-hint
(orearly-hints
, the Fetch spec and Chrome seem to diverge here.)embed
font
link
object
ping
The Fetch spec doesn't include the following type but the Resource Timing note lists it. Is it defined elsewhere?
a
navigation
~ (defined in Navigation Timing)