@@ -87924,6 +87924,10 @@ interface <dfn interface>Location</dfn> { // but see also <a href="#the-location
87924
87924
redirects</dfn></dt>
87925
87925
<dd>a boolean</dd>
87926
87926
87927
+ <dt><dfn data-x="navigation-params-process-response-end-of-body">process response end of
87928
+ body</dfn></dt>
87929
+ <dd>An algorithm expecting a <span data-x="concept-response">response</dd>
87930
+
87927
87931
<dt><dfn data-x="navigation-params-unsafe-start-time">unsafe start time</dfn></dt>
87928
87932
<dd>a number, representing a value of the <span>unsafe shared current time</span> when the
87929
87933
navigation has started</dd>
@@ -87977,8 +87981,8 @@ interface <dfn interface>Location</dfn> { // but see also <a href="#the-location
87977
87981
"<code data-x="">other</code>"), an optional <span data-x="navigation-id">navigation id</span>
87978
87982
<dfn data-x="navigation-navigationid"><var>navigationId</var></dfn> (default null), and an
87979
87983
optional <dfn data-x="navigation-process-end-of-body"><var>processResponseEndOfBody</var></dfn>,
87980
- which is null or an algorithm receiving a <span data-x="concept-response">response</span> (default
87981
- null ):</p>
87984
+ which is an algorithm receiving a <span data-x="concept-response">response</span> (default
87985
+ an algorithm that does nothing ):</p>
87982
87986
87983
87987
<ol>
87984
87988
<li><p>Let <var>unsafeNavigationStartTime</var> be the <span>unsafe shared current time</span>.</p></li>
@@ -88231,8 +88235,11 @@ interface <dfn interface>Location</dfn> { // but see also <a href="#the-location
88231
88235
data-x="navigation-params-reserved-environment">reserved environment</span> is null, <span
88232
88236
data-x="navigation-params-browsing-context">browsing context</span> is
88233
88237
<var>browsingContext</var>, <span data-x="navigation-params-hh">history handling</span> is
88234
- <var>historyHandling</var>, <span data-x="navigation-params-unsafe-start-time">unsafe start
88235
- time</span> is <var>unsafeNavigationStartTime</var>, and <span
88238
+ <var>historyHandling</var>,
88239
+ <span data-x="navigation-params-process-response-end-of-body">process response end of
88240
+ body</span> is <var>processResponseEndOfBody</var>,
88241
+ <span data-x="navigation-params-unsafe-start-time">unsafe start time</span> is
88242
+ <var>unsafeNavigationStartTime</var>, and <span
88236
88243
data-x="navigation-params-has-cross-origin-redirects">has cross-origin redirects</span> is
88237
88244
false.</p></li>
88238
88245
@@ -88291,6 +88298,8 @@ interface <dfn interface>Location</dfn> { // but see also <a href="#the-location
88291
88298
data-x="navigation-params-browsing-context">browsing context</span> is
88292
88299
<var>browsingContext</var>, <span data-x="navigation-params-hh">history handling</span> is
88293
88300
<var>historyHandling</var>,
88301
+ <span data-x="navigation-params-process-response-end-of-body">process response end of
88302
+ body</span> is <var>processResponseEndOfBody</var>,
88294
88303
<span data-x="navigation-params-unsafe-start-time">unsafe start time</span> is
88295
88304
<var>unsafeNavigationStartTime</var>, and <span
88296
88305
data-x="navigation-params-has-cross-origin-redirects">has cross-origin redirects</span> is
@@ -88495,32 +88504,12 @@ interface <dfn interface>Location</dfn> { // but see also <a href="#the-location
88495
88504
<p>Otherwise:</p>
88496
88505
88497
88506
<ol>
88498
- <li><p>Let <var>finalResponseReached</var> be false.</p></li>
88499
-
88500
88507
<li><p>If <var>response</var> is null, <!--FETCH--><span
88501
88508
data-x="concept-fetch">fetch</span> <var>request</var>.</p></li>
88502
88509
88503
88510
<li><p>Otherwise, perform <span>HTTP-redirect fetch</span> using
88504
88511
<var>request</var> and <var>response</var>.</p></li>
88505
88512
88506
- <li><p>Let <var>onFinalResponseReached</var> be to set <var>finalResponseReached</var> to
88507
- true.</p></li>
88508
-
88509
- <li>
88510
- <p>When the task to <i data-x="processResponseEndOfBody">processResponseEndOfBody</i>
88511
- is posted on the <span>networking task source</span>, perform the following steps:</p>
88512
-
88513
- <ol>
88514
- <li><p>If <var>processResponseEndOfBody</var> is null, then return.
88515
-
88516
- <li><p>If <var>finalResponseReached</var> is true, then call
88517
- <var>processResponseEndOfBody</var> given <var>response</var>.</p>
88518
-
88519
- <li><p>Otherwise, set <var>onFinalResponseReached</var> to
88520
- <var>processResponseEndOfBody</var>.</p></li>
88521
- </ol>
88522
- </li>
88523
-
88524
88513
<li><p>Wait for the <span data-x="concept-task">task</span> on the <span>networking task
88525
88514
source</span> to <span>process response</span> and set <var>response</var> to the
88526
88515
result.</p></li>
@@ -88628,8 +88617,6 @@ interface <dfn interface>Location</dfn> { // but see also <a href="#the-location
88628
88617
URL scheme</span> given <var>locationURL</var>, <var>browsingContext</var>,
88629
88618
<var>sandboxFlags</var>, and <var>hasTransientActivation</var>, and return.</p></li>
88630
88619
88631
- <li><p>Call <var>onFinalResponseReached</var> with <var>response</var>.</p></li>
88632
-
88633
88620
<li><p>Let <var>responsePolicyContainer</var> be the result of <span>creating a policy container
88634
88621
from a fetch response</span> given <var>response</var> and <var>request</var>'s <span
88635
88622
data-x="concept-request-reserved-client">reserved client</span>.</p></li>
@@ -88655,6 +88642,8 @@ interface <dfn interface>Location</dfn> { // but see also <a href="#the-location
88655
88642
data-x="navigation-params-browsing-context">browsing context</span> is
88656
88643
<var>browsingContext</var>, <span data-x="navigation-params-hh">history handling</span> is
88657
88644
<var>historyHandling</var>,
88645
+ <span data-x="navigation-params-process-response-end-of-body">process response end of body</span>
88646
+ is <var>processResponseEndOfBody</var>,
88658
88647
<span data-x="navigation-params-unsafe-start-time">unsafe start time</span> is
88659
88648
<var>unsafeNavigationStartTime</var>, and
88660
88649
<span data-x="navigation-params-has-cross-origin-redirects">has cross-origin redirects</span> is
@@ -88710,6 +88699,8 @@ interface <dfn interface>Location</dfn> { // but see also <a href="#the-location
88710
88699
<p>If <var>failure</var> is true, then:</p>
88711
88700
88712
88701
<ol>
88702
+ <li><p>Call <var>processResponseEndOfBody</var> with <var>response</var>.</p></li>
88703
+
88713
88704
<li><p><span data-x="navigate-ua-inline">Display the inline content with an appropriate error
88714
88705
shown to the user</span> given <var>browsingContext</var>.</p></li>
88715
88706
@@ -88734,7 +88725,9 @@ interface <dfn interface>Location</dfn> { // but see also <a href="#the-location
88734
88725
</li>
88735
88726
88736
88727
<li><p>If <var>response</var>'s <span data-x="concept-response-status">status</span> is 204 or
88737
- 205, then return.</p></li>
88728
+ 205, then call <var>navigationParams</var>'s
88729
+ <span data-x="navigation-params-process-response-end-of-body">process response end of body</span>
88730
+ and return.</p></li>
88738
88731
<!-- Theoretically, HTTP 205 processing would occur here, resetting all forms with no other
88739
88732
effect. However, it seems nobody actually wants to use this ability, so requiring it here
88740
88733
seems like unnecessary work. -->
@@ -89489,8 +89482,16 @@ new PaymentRequest(…); // Allowed to use
89489
89482
89490
89483
<p>When no more bytes are available, the user agent must <span>queue a global task</span> on the
89491
89484
<span>networking task source</span> given the newly-created <code>Document</code>'s <span>relevant
89492
- global object</span> for the parser to process the implied EOF character, which eventually causes
89493
- a <code data-x="event-load">load</code> event to be fired.</p>
89485
+ global object</span> to the following:</p>
89486
+
89487
+ <ol>
89488
+ <li><p>Call <var>navigationParams</var>'s
89489
+ <span data-x="navigation-params-process-response-end-of-body">process response end of body</span>
89490
+ with <var>navigationParams</var>'s <span data-x="navigation-params-response">response</span>.</p>
89491
+
89492
+ <li><p>Let the parser to process the implied EOF character, which eventually causes
89493
+ a <code data-x="event-load">load</code> event to be fired.</p></li>
89494
+ </ol>
89494
89495
89495
89496
<p>After creating the <code>Document</code> object, but before any script execution, certainly
89496
89497
before the parser <span data-x="stop parsing">stops</span>, the user agent must <span>update the
@@ -89530,6 +89531,12 @@ new PaymentRequest(…); // Allowed to use
89530
89531
this before the complete document has been parsed (thus achieving <i>incremental rendering</i>),
89531
89532
and must do this before any scripts are to be executed.</p>
89532
89533
89534
+ <p>When no more bytes are available, the user agent must <span>queue a global task</span> on the
89535
+ <span>networking task source</span> given <var>document</var>'s <span>relevant
89536
+ global object</span> to call <var>navigationParams</var>'s
89537
+ <span data-x="navigation-params-process-response-end-of-body">process response end of body</span>
89538
+ with <var>navigationParams</var>'s <span data-x="navigation-params-response">response</span>.</p>
89539
+
89533
89540
<p>Once parsing is complete, the user agent must set <var>document</var>'s <span
89534
89541
data-x="concept-document-navigation-id">navigation id</span> to null.</p>
89535
89542
@@ -89587,8 +89594,16 @@ new PaymentRequest(…); // Allowed to use
89587
89594
89588
89595
<p>When no more bytes are available, the user agent must <span>queue a global task</span> on the
89589
89596
<span>networking task source</span> given the newly-created <code>Document</code>'s <span>relevant
89590
- global object</span> for the parser to process the implied EOF character, which eventually causes
89591
- a <code data-x="event-load">load</code> event to be fired.</p>
89597
+ global object</span> to the following:</p>
89598
+
89599
+ <ol>
89600
+ <li><p>Call <var>navigationParams</var>'s
89601
+ <span data-x="navigation-params-process-response-end-of-body">process response end of body</span>
89602
+ with <var>navigationParams</var>'s <span data-x="navigation-params-response">response</span>.</p>
89603
+
89604
+ <li><p>Let the parser to process the implied EOF character, which eventually causes a
89605
+ <code data-x="event-load">load</code> event to be fired.</p></li>
89606
+ </ol>
89592
89607
89593
89608
<p>After creating the <code>Document</code> object, but potentially before the page has finished
89594
89609
parsing, the user agent must <span>update the session history with the new page</span> given
@@ -89694,6 +89709,11 @@ new PaymentRequest(…); // Allowed to use
89694
89709
script, to give the document a <code>title</code>, or to make the media <span
89695
89710
data-x="attr-media-autoplay">autoplay</span>.</p>
89696
89711
89712
+ <p>When no more bytes are available, the user agent must <span>queue a global task</span> on the
89713
+ <span>networking task source</span> given the newly-created <code>Document</code>'s <span>relevant
89714
+ global object</span> to call <var>navigationParams</var>'s
89715
+ <span data-x="navigation-params-process-response-end-of-body">process response end of body</span>
89716
+ with <var>navigationParams</var>'s <span data-x="navigation-params-response">response</span>.</p>
89697
89717
89698
89718
<h4 id="read-plugin"><dfn data-x="navigate-plugin">Page load processing model for content that uses plugins</dfn></h4>
89699
89719
@@ -89769,6 +89789,8 @@ new PaymentRequest(…); // Allowed to use
89769
89789
result</span> is a new <span data-x="coop-enforcement-result">cross-origin opener policy
89770
89790
enforcement result</span>, <span
89771
89791
data-x="navigation-params-reserved-environment">reserved environment</span> is null,
89792
+ <span data-x="navigation-params-process-response-end-of-body">process response end of body</span>
89793
+ is an algorithm that does nothing,
89772
89794
<span data-x="navigation-params-unsafe-start-time">unsafe start time</span> is the
89773
89795
<span>unsafe shared current time</span>, and
89774
89796
<span data-x="navigation-params-browsing-context">browsing context</span> is
0 commit comments