Add "same origin with its ancestors" #10559
Conversation
See discussion in w3c/webappsec-credential-management#253.
domenic
added
topic: origin
integration
There was a problem hiding this comment.
Nice!
Now I wonder, do we want this or do we want an algorithm that returns one of the following tokens: w3c/webappsec-fetch-metadata#89 (comment) (probably the second set of tokens there)?
Though perhaps having both is good and this can be refactored later on top of the more generic ancestor relationship algorithm.
| @@ -96505,6 +96500,35 @@ interface <dfn interface>NotRestoredReasons</dfn> { | |||
| <li><p>Return <var>navigables</var>.</p></li> | |||
| </ol> | |||
|
|
|||
| <p class="note">These descendant-collecting algorithms are described as looking at the DOM tree | |||
|
Ditto to Anne's desire to match those enums. I stumbled across this from trying to help draft a Fetch change that uses Anne and Johann's new cookie spec draft. I was searching for this old PR, but having the enum Anne proposed here would be better. |
|
cc @sjledoux who is working on these headers on our side |
|
Let me close this, as the people in the OP never responded to tell me if this would be helpful, and if there are new cases for some version of this, I think someone else will need to do the work :) |
See discussion in w3c/webappsec-credential-management#253.
@nsatragno @timcappalli @marcoscaceres let me know if this works for your specs?
/document-sequences.html ( diff )