Ilya Grigorik

@yoavweiss assigning you as owner on this; I believe you had an AI from the F2F to write up how different browsers behave, what we want to see, etc?

Thanks for unpacking the use cases. Overall, I _think_ this direction makes sense, but a few questions as I'm thinking through it... (A) Likely outcome is that an analytics script...

> A. They could use separate observers or they could observe both types in one observer. I don't think we're solving the problem of figuring out when an SPA nav...

> Yea, for the SPA use case, in order to avoid having permanent observers we'd need to support the buffered flag to work after onload. It could be something like:...

@nicjansma thanks, that makes sense. This also suggests that we shouldn't need any additional acrobatics for additional buffered flags or modes, which addresses my earlier concerns. @rniwa @toddreifsteck would love...

The analysis on missing resources and unattributed bytes definitely motivates the need for an investigation (and a solution :)) in this space. Thank you for the thorough job on the...

I'm assuming you're using XHR to invoke the upload - correct? Is there any reason why you can't instrument the upload logic to get the method and/or any other variables...

On further thought.. I think this a subset of multi-request case that we need to address, see: https://lists.w3.org/Archives/Public/public-web-perf/2015Feb/0059.html

The behavior you're describing is correct: browsers cache CORS permissions responses to avoid having to send an OPTIONS request for each cross-origin fetch. Hence the "odd" number of requests. That...

Discussed on perf call (26/08/15): @toddreifsteck to followup with list of initiators implemented in Edge.