Noam Rosenthal

> I think the simplest solution here (as also suggested upthread by mnot) would be that we take CSP into account for each 103 response individually. So if the server...

Does [wasDiscurded](https://wicg.github.io/page-lifecycle/#dom-document-wasdiscarded) help you here? This seems somewhat related to https://github.com/w3c/navigation-timing/issues/178

> Thanks @Krinkle for reporting. Transferred issue to the navigation timing repo, at it's actually CSS that is directly in the spec that is causing this issue: > > https://github.com/w3c/navigation-timing/blob/606cf02fb6639d186a168895c78e88d68490d937/index.html#L9-L15...

I believe it's time to remove those "obsolete" things from the spec, and defer to old versions. But if there are differing views about this, we should discuss of course...

Ah it's deprecated but still available, I misunderstood. If it's available in older versions of the spec, I suggest to refer to the old version from the new one and...

Gotcha, lots of TIL here for me. Not sure what this process entails, will defer to @yoavweiss.

> * [ ] "Obsolete" may not be the accurate term for what we're trying to convey - we want to document the APIs and their processing, but discourage developers...

@yoavweiss @annevk @npm1 @sefeng211 @achristensen07

> If "current origin redirect chain" means the origin boundary is not crossed therein, that option seems reasonable to me. Yes, it means something like "after all the redirects that...

Note that (3) includes (2) inside it, in the cases where TAO headers are not there. With option 3 I want to be careful when we overload the meaning of...