这是indexloc提供的服务，不要输入任何密码
Skip to content

Add note about pending configs #87

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.

Sign up for GitHub

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

Merged
merged 6 commits into from
May 16, 2023
Merged

Add note about pending configs #87

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
59fec48
Add note about pending configs
gtanzer May 15, 2023
6c40126
Oops
gtanzer May 15, 2023
1616986
Slight rephrase
gtanzer May 15, 2023
e219d65
Update spec.bs
domfarolino May 16, 2023
2094ce3
Update spec.bs
domfarolino May 16, 2023
78f5b0f
Fix build
domfarolino May 16, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions spec.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -410,6 +410,16 @@ A <dfn>fenced frame config mapping</dfn> has three submappings:
configs=]
</dl>

Note: The purpose of pending configs is to enable config-generating APIs to resolve configs
asynchronously in a way that doesn't create timing side channels, i.e., the pending config is
returned to the web platform in a constant amount of time, before any computation whose duration
depends on cross-site data. Because the privacy of this depends on the web platform not being able
to discern when a pending config is finalized, it is important that all visibilities and values of
transparent fields do not change from the pending config to the finalized config, given that they
can be inspected through {{FencedFrameConfig}}'s getters. Therefore, a {{FencedFrameConfig}} that
is created and exposed to the web platform is effectively immutable even if its underlying
[=fencedframeconfig/config=] is technically "pending", and will finish resolving completely later.

Each [=fenced frame config mapping=] has a <dfn for="fenced frame config mapping">maximum number of
configs</dfn>, which is implementation-defined. The [=fenced frame config mapping/maximum number of
configs=] may be a nonnegative number or infinity.
Expand Down