Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Spec] Fix navigation from the default constructor not installing a fenced frame config. #183

Merged
merged 11 commits into from
Oct 5, 2024
Prev Previous commit
Next Next commit
fix outdated naming
  • Loading branch information
blu25 committed Aug 27, 2024
commit 832bd5c2cc174e3ebed4b6aed536a7049fdc4420
6 changes: 3 additions & 3 deletions spec.bs
Original file line number Diff line number Diff line change
Expand Up @@ -2903,13 +2903,13 @@ CORP violation report=] algorithm, as leaving it unfenced may cause a privacy le
: [=mapped url/visibility=]
:: [=visibility/transparent=]

: [=fenced frame config/effective sandbox flags=]
: [=fenced frame config/effective sandboxing flags=]
:: a [=struct=] with the following [=struct/items=]:

: [=effective sandbox flags/value=]
: [=effective sandboxing flags/value=]
:: The [=fencedframetype/default fenced frame effective sandboxing flags=].

: [=effective sandbox flags/visibility=]
: [=effective sandboxing flags/visibility=]
:: [=visibility/opaque=]

: [=fenced frame config/effective enabled permissions=]
Expand Down
Loading