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