Processing Model chart is missing domLoading marker about navigation-timing HOT 10 CLOSED

@plehegar we have https://github.com/w3c/navigation-timing/blob/gh-pages/timing-overview.png checked in, which reflects all the right marks, but we have an SVG in the spec. Any objections to linking to the PNG? Do we have a doc / source for the png? Is that the PPT?

from navigation-timing.

Also missing: workerStart.

from navigation-timing.

No objection from me. The original drawing was indeed the PPT.

from navigation-timing.

I'm proposing we update NT with the following:

• domLoading is part of NT1 and we deprecated it in NT2, hence that's a no-op.
• Instead of replicating all of the RT timestamps, I propose we defer those to ResourceTiming (which includes workerStart)

The above would cleanly reflect what we define for PerformanceNavigationTiming and keeps things tidy between specs -- e.g. if we update RT, we don't have to duplicate diagram changes to NT.

@plehegar @toddreifsteck any objections?

from navigation-timing.

SGTM. Maybe also add a link to the corresponding RT diagram?

from navigation-timing.

Yeah, that one also needs to be updated and we can add a link to it in the figure caption.

from navigation-timing.

While working on updating the RT diagram... here's another variant with RT visible:

@toddreifsteck @plehegar any preference for one vs the other?

from navigation-timing.

I, personally, like the 2nd one. I recommend labelling the Resource Timings section by connecting the sections with a line wrapping both ends going down then joining on a Resource Timings label to make it clear. But... just my opinion. :-) @nolanlawson

from navigation-timing.

I like the 2nd one but it duplicates information with RT. We'll get it out of sync at some point in the future,...

from navigation-timing.

@plehegar in #52 I link to the source (in an HTML comment), which contains both diagrams.. Arguably, when they're in the same doc, it's easier to remember to keep them in sync. That said, I can be convinced either way.

@toddreifsteck I'll let you decide this one :) If you like #52, merge it. Otherwise, I can update it with the first diagram.

from navigation-timing.