search

w3c / server-timing

Server Timing
http://w3c.github.io/server-timing/
Other
75 stars 20 forks source link

remove empty anchor #50

Closed cvazac closed 6 years ago

cvazac commented 6 years ago

screen shot 2018-01-16 at 1 57 44 pm

Preview | Diff

cvazac commented 6 years ago

@igrigorik It was certainly meant to link to something, but https://w3c.github.io/resource-timing/#cross-origin-resources didn't fit for me. The server timing bits tell me .serverTiming shouldn't be exposed on ResourceTimingEntry objects. The link refers to durations being zeroed out. Or maybe the resource-timing bits should be updated and fix link.

yoavweiss commented 6 years ago

Yeah, the behavior we ended up with for crossorigin server timing with no TAO seems significantly different than what we had for ResourceTiming.

igrigorik commented 6 years ago

Yeah, the behavior we ended up with for crossorigin server timing with no TAO seems significantly different than what we had for ResourceTiming.

I'm confused.. Per https://w3c.github.io/server-timing/#processing-model, we talk about doing a check against timing-allow-origin algorithm. So, it's same as RT — correct? That said, re-reading this particular update, I agree that cross-origin link is probably unnecessary.

cvazac commented 6 years ago

As the spec reads today, a cross origin resource will have: 

{
  ...
  serverTiming: []
}

Previous versions of the spec had "zeroed out" entries:

{
  ...
  serverTiming: [{
    name: 'blah', 
    duration: 0, 
    description: ''
  }, ... ]
}