@@ -7028,6 +7028,8 @@ descendants share a quota of 384 kibibytes. That value is computed as such:
7028
7028
7029
7029
<dl class=switch>
7030
7030
<dt><var> isTopLevel</var> is true and <var> deferredFetchAllowed</var> is false
7031
+ <dt><var> isTopLevel</var> is false, and <var> deferredFetchAllowed</var> is false, and
7032
+ <var> deferredFetchMinimalAllowed</var> is false
7031
7033
<dd> 0
7032
7034
7033
7035
<dt><var> isTopLevel</var> is true and <var> deferredFetchMinimalAllowed</var> is false
@@ -7095,11 +7097,11 @@ descendants share a quota of 384 kibibytes. That value is computed as such:
7095
7097
7096
7098
<p class=note> This is called on navigation, when the source document of the navigation is the
7097
7099
<a for=/>navigable</a> 's parent document. It potentially reserves either 64kb or 8kb of quota for
7098
- the container and its navigable, if allowed permissions policy. It is not observable to the
7100
+ the container and its navigable, if allowed by permissions policy. It is not observable to the
7099
7101
cotnainer document whether the reserved quota was used in practice. This algorithm assumes that the
7100
- container's document might delegate quota to the navigated frame , and the reserved quota would only
7101
- apply in that case, and would be ignored if it ends up being shared. If quota was reserved and the
7102
- document ends up being <a>same origin</a> with its parent, the quota would be
7102
+ container's document might delegate quota to the navigated container , and the reserved quota would
7103
+ only apply in that case, and would be ignored if it ends up being shared. If quota was reserved and
7104
+ the document ends up being <a>same origin</a> with its parent, the quota would be
7103
7105
<a data-lt="potentially free deferred-fetch quota">freed</a> .
7104
7106
7105
7107
<ol>
0 commit comments