search

w3c / resource-timing

Resource Timing
https://w3c.github.io/resource-timing/
Other
119 stars 35 forks source link

Illustrate in diagram that timestamps are not necessarily consecutive #323

Closed noamr closed 2 years ago

noamr commented 2 years ago

Closes #164

yoavweiss commented 2 years ago

Thanks! I'm not sure "stall" is the best word to describe the delays that can be incurred from the browser exceeding the DNS, TCP/QUIC connection and in-slight request limits. Maybe a "potential delay" bubble below, with arrows pointing to before the DNS, TCP/QUIC and request squares?

noamr commented 2 years ago

Thanks! I'm not sure "stall" is the best word to describe the delays that can be incurred from the browser exceeding the DNS, TCP/QUIC connection and in-slight request limits. Maybe a "potential delay" bubble below, with arrows pointing to before the DNS, TCP/QUIC and request squares?

What's the word used for this in DevTools? I want to use the same vocabulary

yoavweiss commented 2 years ago

Chrome DevTools indeed uses the word "stalled" for the connection parts, but doesn't talk about other types of delays. IMO, it's inaccurate, but there's no point in bikeshedding the diagram, as it's easy to change it in the future if complaints come in.

What about changing it to a single bubble pointing it at the 3 potential locations?