You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: proposals/hasCrossSiteAncestor.md
+5-1
Original file line number
Diff line number
Diff line change
@@ -104,17 +104,21 @@ string. A UUID of the document.
104
104
105
105
| Required Combinations | Notes |
106
106
|---|---|
107
-
|frameId | frameId must be a non-zero value|
108
107
|tabId + frameId |frameId can be 0|
109
108
|tabId | will use the top-level frame (frameId 0)|
109
+
|frameId| frameId must not be 0, when specified without tabId|
110
110
|documentId| tabId/frameId are not required but permitted|
111
111
112
112
##### Return value
113
113
A Promise that will be fulfilled with a `Cookie.partitionKey` object that matches the properties given in the details parameter and contains the `hasCrossSiteAncestor` value associated with the current cross-site status of the frame.
114
114
115
+
##### Permissions required to use Cookies.getPartitionKey()
116
+
- Host permissions for the frame's document.
117
+
115
118
##### Error conditions
116
119
- If host permissions are not granted for the document whose partitionkey is getting queried an error will be returned.
117
120
- When the parameters passed do not correspond to an existing frame, an error will be returned.
121
+
- If the partitionKey that would be associated with the frame can not be serialized an error will be returned. This can happen when the origin associated with the topLevelSite is opaque or if the underlying key associated with the frame has a nonce. This is comparable to situations where `document.cookie` would throw.
0 commit comments