Conversation
index.html
Outdated
| to the empty string. | ||
| {{PerformanceResourceTiming/secureConnectionStart}}. Further, the | ||
| {{PerformanceResourceTiming/nextHopProtocol}} attribute will be set | ||
| to the empty string. |
There was a problem hiding this comment.
I think the wording is still somewhat confusing here as the attributes are not set. Rather the getters end up returning 0 or the empty string or whatever due to the underlying data not revealing anything.
| data-cite="HTML#cors-cross-origin">CORS-cross-origin</a>. | ||
|
|
||
| {{PerformanceResourceTiming/transferSize}} is affected both by the <a data-cite="FETCH#concept-tao-check">timing | ||
| allow check</a> and by the <a data-cite="HTML#cors-cross-origin">CORS-cross-origin</a> status. |
There was a problem hiding this comment.
It's mostly a function of encodedBodySize so wouldn't this apply to encodedBodySize as well?
There was a problem hiding this comment.
I don't quite understand?
There was a problem hiding this comment.
What makes https://w3c.github.io/resource-timing/#dom-performanceresourcetiming-transfersize affected by the timing allow check, but https://w3c.github.io/resource-timing/#dom-performanceresourcetiming-encodedbodysize not?
There was a problem hiding this comment.
transferSize is a function of something that comes from response's body info and cache state. cache state is specifically zeroed by TAO-fail here (4.2.5) and body-info isn't.
There was a problem hiding this comment.
Right, but that means the timing allow check equally applies to encodedBodySize, no?
There was a problem hiding this comment.
No, encodedBodySize is only affected by CORS check as it doesn't look at cache state.
There was a problem hiding this comment.
Oh I see, the cache state is zeroed due to allow timing.
Where is body info masked though?
There was a problem hiding this comment.
| of fetching the resource, and do not go through the <a data-cite="FETCH#concept-tao-check">timing | ||
| allow check</a>. | ||
| To get the full information about those fetches, the service worker's own performance timeline | ||
| can be inspected. [[SERVICE-WORKERS]] |
There was a problem hiding this comment.
Some hint of where the requirements can be found about how the forwarding happens would be useful I think.
2 participants
Closes #423.
Preview | Diff