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
/// and [Content-Security-Policy frame-ancestors directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors).
211
213
/// If set, a frame ancestor is allowed if it is allowed by the additional allowed frame
212
214
/// ancestoers or original http header from the site.
213
215
/// Whether an ancestor is allowed by the additional allowed frame ancestoers is done the same way as if the site provided
214
216
/// it as the source list of the Content-Security-Policy frame-ancestors directive.
215
217
/// For example, if `https://example.com` and `https://www.example.com` are the origins of the top
216
-
/// page and intemediate iframes that embed a nested siteembedding iframe, and you fully trust
217
-
/// those origins, you should set thus property to `https://example.com https://www.example.com`.
218
+
/// page and intemediate iframes that embed a nested site-embedding iframe, and you fully trust
219
+
/// those origins, you should set this property to `https://example.com https://www.example.com`.
218
220
/// This property gives the app the ability to use iframe to embed sites that otherwise
219
221
/// could not be embedded in an iframe in trusted app pages.
220
222
/// This could potentially subject the embedded sites to [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking)
0 commit comments