diff --git a/source b/source index 9aed02e8141..8a1f9968a4f 100644 --- a/source +++ b/source @@ -2527,6 +2527,7 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
User-Agent
` valueRequestCredentials
enumerationRequestDestination
enumerationfetch()
methodFetch request with initiatorType set to initiatorType, processResponseConsumeBody set to the following steps given response response:
Finalize and report timing with response, - el's node document's relevant global object, and - initiatorType.
If response is a network error or its status is not an ok @@ -24956,12 +24958,8 @@ document.body.appendChild(wbr);
Fetch request, with processResponseEndOfBody given response res set to finalize and report
- timing with res, settingsObject's global object, and "ping
".
Fetch request,
+ with initiatorType set to "ping
".
This may be done in parallel with the primary fetch, and is independent of the @@ -26508,8 +26506,6 @@ document.body.appendChild(wbr); options's base URL. If that fails, then return. Otherwise let url be the resulting URL record.
Let unsafeEndTime be 0.
Let response be "pending
".
Let request be the result of creating a preload key given request.
Let finalize be the following step given a Document
- document and a response response:
- finalize and report timing given response,
- document's relevant global object, options's
- initiator, and unsafeEndTime.
Let initiatorType be "early hint
" if
+ options's document is "pending
", otherwise "link
".
Let controller be null.
Let reportTiming given a Document
document be to
+ report timing for controller given document's
+ relevant global object.
Fetch request, with Set controller to the result of fetching request, with initiatorType set to initiatorType and processResponseConsumeBody set to the following steps given a response response and null, failure, or a byte sequence bytesOrNull:
@@ -26560,11 +26562,9 @@ document.body.appendChild(wbr);Otherwise, set response to a network error.
Set unsafeEndTime to the unsafe shared current time.
If options's document is not - null, then call finalize given options's document and response.
If entry's on response available is null, then set entry's response is not null, then - call finalize given document and entry's - response.
Set document's map of preloaded resources[key] to entry.
Fetch the image: Fetch request. Return +
Fetch the image: Fetch request with
+ initiatorType set to "img
". Return
from this algorithm, and run the remaining steps as part of the fetch's processResponse for the response
response.
Let finalize image loading given eventName be the following:
- -Finalize and report timing with response, the img
- element's node document's relevant global object, and "img
".
Fire an event named eventName at
- the img
element.
Let finalize image loading given eventName be to Fire an event named eventName at the
+ img
element.
As soon as possible, jump to the first applicable entry from the following list:
@@ -32074,21 +32065,11 @@ interface HTMLIFrameElement : HTMLElement { document is not completely loaded, then set historyHandling to "replace
".Let reportFrameTiming be the following step given response response: queue an element - task on the networking task source given element's node - document's relevant global object to finalize and report timing - given response, element's node document's relevant - global object, and element's local - name.
Navigate element's nested browsing context to resource, with historyHandling set to historyHandling, the + data-x="navigation-hh">historyHandling set to historyHandling, and the source browsing context set to element's node document's - browsing context, and - processResponseEndOfBody set to - reportFrameTiming.
navigate
", and whose use-URL-credentials flag is set.
- Let processResponseEndOfBody given response res be to finalize and report
- timing with res, element's node document's
- relevant global object, and "embed
".
Fetch request, with processResponseEndOfBody set to - processResponseEndOfBody, and processResponse set - to the following steps given response - response:
+ data-x="initiatorType">initiatorType set to "embed
", processResponse set to the following steps given response response:
If another task has since been queued to run @@ -33154,11 +33129,8 @@ interface HTMLObjectElement : HTMLElement { data-x="">navigate", and whose use-URL-credentials flag is set.
Fetch request, with processResponseEndOfBody given response res set to finalize and report
- timing with res, the element's node document's
- relevant global object, and "object
".
Fetch request with initiatorType set to "object
".
Fetching the resource must delay the load event of the element's node
@@ -33668,13 +33640,9 @@ interface HTMLVideoElement : HTMLMediaElement
data-x="concept-request-credentials-mode">credentials mode is "include
", and whose use-URL-credentials flag is set.
-
Fetch request, with
- processResponseEndOfBody given
- response res set to
- finalize and report timing with res, the element's
- node document's relevant global object, and
- "video
". This must delay the load event of the element's
- node document.
Fetch request, with initiatorType set to "video
". This must
+ delay the load event of the element's node document.
Fetch request, with - processResponse set to the following steps given +
Fetch request with + initiatorType set to destination, and processResponse set to the following steps given response response:
Let finalize be to finalize and report timing with - response, global, and destination, and call - updateMedia.
Fetch request with initiatorType set to destination.
-Let processEndOfMedia be the following steps:
- -Call finalize.
- -If the fetching process has completes without errors, including decoding the - media data, and if all of the data is available to the user agent without network - access, then, the user agent must move on to the final step below. - This might never happen, e.g. when streaming an infinite resource such as web radio, or - if the resource is longer than the user agent's ability to cache data.
-Let processEndOfMedia be the following steps: If the fetching process has + completes without errors, including decoding the media data, and if all of the data is + available to the user agent without network access, then, the user agent must move on to + the final step below. This might never happen, e.g. when streaming an infinite + resource such as web radio, or if the resource is longer than the user agent's ability to + cache data.
If the result of verifying
response given the current media resource and
@@ -38764,11 +38725,8 @@ interface VideoTrack {
track
element's node document's relevant settings
object.
Fetch request, with processResponseEndOfBody given response res set to finalize and report
- timing with res, the element's node document's relevant
- global object, and "track
".
Fetch request with initiatorType set to "track
".
The tasks queued by the
@@ -49743,28 +49701,19 @@ ldh-str = < as defined in credentials mode is "include
", and whose use-URL-credentials flag is set.
Fetch request, with - processResponseEndOfBody set to the following steps - given response response:
- -Finalize and report timing with response, the input
- element's node document's relevant global object, and
- "input
".
If the download was successful and the image is
- available, queue an element task on the
- user interaction task source given the input
element to
- fire an event named
- load
at the input
element; and otherwise, if the
- fetching process fails without a response from the remote server, or completes but the image is
- not a valid or supported image, queue an element task on the user interaction
- task source given the input
element to
- fire an event named
- error
on the input
element.
Fetch request, with initiatorType set to "input
", and processResponseEndOfBody set to the following step
+ given response response: If the download was
+ successful and the image is available,
+ queue an element task on the user interaction task source given the
+ input
element to fire an event named
+ load
at the input
element; and otherwise, if the
+ fetching process fails without a response from the remote server, or completes but the image is
+ not a valid or supported image, queue an element task on the user interaction
+ task source given the input
element to
+ fire an event named
+ error
on the input
element.
Document
, once it has been createdother
"), an optional navigation id
- navigationId (default null), and an
- optional processResponseEndOfBody,
- which is an algorithm receiving a response (default an
- algorithm that does nothing):
+ "other
"), and an optional navigation id
+ navigationId (default null):
If resource is a URL, then set resource to a new Location { // but see also browsing context is browsingContext, history handling is historyHandling, process response end of body - is processResponseEndOfBody, has cross-origin redirects is - false, and fetch controller is + null, and commit early hints is null.
Run process a navigate response with navigationType, @@ -89110,10 +89054,10 @@ interface Location { // but see also browsing context is browsingContext, history handling is historyHandling, process response end of body - is processResponseEndOfBody, has cross-origin redirects is - false, and fetch controller is + null, and commit early hints is null.
Run process a navigate response with navigationType,
@@ -89323,9 +89267,27 @@ interface Location { // but see also fetch request, with
- processEarlyHintsResponse set to the following step
+ Let fetchController be null. Let timingGlboal be null. Let initiatorType be null. If browsingContext's container document is not null and
+ browsingContext's container document's
+ browsing context is
+ sourceBrowsingContext, then set timingGlobal to
+ browsingContext's container document's
+ relevant global object and set initiatorType to
+ browsingContext's container's local name. If response is null, set fetchController to the result of
+ fetching request, with initiatorType set to initiatorType timingGlobal set to timingGlobal, and processEarlyHintsResponse set to the following step
given a response earlyResponse: If
commitEarlyHints is null, then set commitEarlyHints to the result
of processing early hint headers given
@@ -89467,10 +89429,10 @@ interface Location { // but see also browsing context is
browsingContext, history handling is
historyHandling, process response end of body is
- processResponseEndOfBody,
- has cross-origin redirects is
- hasCrossOriginRedirects, and
+ data-x="navigation-params-has-cross-origin-redirects">has cross-origin redirects is
+ hasCrossOriginRedirects, fetch controller is
+ fetchController, and
commit early hints is
commitEarlyHints.
Display the inline content with an appropriate error shown to the user given browsingContext.
Create the navigation timing entry for document, with
- navigationParams's response's timing info, redirectCount,
- navigationTimingType, and navigationParams's If navigationParams's fetch controller is not null, then
+ create the navigation timing entry for document, with the result of
+ extracting the full timing info from
+ navigationParams's fetch controller, redirectCount,
+ navigationTimingType, navigationParams's response's service worker timing info.
If navigationParams's response @@ -90313,16 +90275,8 @@ new PaymentRequest(…); // Allowed to use
When no more bytes are available, the user agent must queue a global task on the
networking task source given the newly-created Document
's relevant
- global object to run the following steps:
Call navigationParams's process response end of body with - navigationParams's response.
- -Have the parser process the implied EOF character, which eventually causes a load
event to be fired.
load
event to be fired.
After creating the Document
object, but before any script execution, certainly
before the parser stops, the user agent must update the
@@ -90362,12 +90316,6 @@ new PaymentRequest(…); // Allowed to use
this before the complete document has been parsed (thus achieving incremental rendering),
and must do this before any scripts are to be executed.
When no more bytes are available, the user agent must queue a global task on the - networking task source given document's relevant global - object to call navigationParams's process response end of body with - navigationParams's response.
-Once parsing is complete, the user agent must set document's navigation id to null.
@@ -90425,16 +90373,8 @@ new PaymentRequest(…); // Allowed to useWhen no more bytes are available, the user agent must queue a global task on the
networking task source given the newly-created Document
's relevant
- global object to run the following steps:
Call navigationParams's process response end of body with - navigationParams's response.
- -Have the parser process the implied EOF character, which eventually causes a load
event to be fired.
load
event to be fired.
After creating the Document
object, but potentially before the page has finished
parsing, the user agent must update the session history with the new page given
@@ -90540,12 +90480,6 @@ new PaymentRequest(…); // Allowed to use
script, to give the document a title
, or to make the media autoplay.
When no more bytes are available, the user agent must queue a global task on the
- networking task source given the newly-created Document
's
- relevant global object to call navigationParams's process response end of body with
- navigationParams's response.
When a resource that requires an external resource to be rendered is to be loaded, provided @@ -90619,9 +90553,7 @@ new PaymentRequest(…); // Allowed to use opener policy, COOP enforcement result is a new cross-origin opener policy enforcement result, reserved - environment is null, process response end of body is - an algorithm that does nothing, and is null, and browsing context is browsingContext.
@@ -93346,19 +93278,16 @@ document.querySelector("button").addEventListener("click", bound); complete with response response, run the remaining steps. -Otherwise, fetch request. Return from this
- algorithm, and run the remaining steps as part of the fetch's processResponseConsumeBody given Otherwise, fetch request with initiatorType set to "script
". Return from this algorithm, and run the remaining steps as part of the
+ fetch's processResponseConsumeBody given response response.
response can be either CORS-same-origin or CORS-cross-origin. This only affects how error reporting happens.
Finalize and report timing with response, settings
- object's global object, and "script
".
Set response to response's unsafe response.
Otherwise, fetch request. Return from this +
Otherwise, fetch request with initiatorType set to "other
". Return from this
algorithm, and run the remaining steps as part of the fetch's processResponseConsumeBody given response response.
Finalize and report timing with response, fetch client
- settings object's global object, and
- "other
".
Set response to response's unsafe response.
Otherwise, fetch request, and let +
Otherwise, fetch request with initiatorType set to "other
", and let
response be the result.
Unlike other algorithms in this section, the fetching process is synchronous @@ -93502,10 +93429,6 @@ document.querySelector("button").addEventListener("click", bound); also finish their work synchronously.
Finalize and report timing with response, settings
- object's global object, and "other
".
Set response to response's unsafe response.
Otherwise, fetch request. Return from this
- algorithm, and run the remaining steps as part of the fetch's Otherwise, fetch request with initiatorType set to "other
". Return from
+ this algorithm, and run the remaining steps as part of the fetch's processResponseConsumeBody given response response.
response is always CORS-same-origin.
Finalize and report timing with response, fetch client
- settings object's global object, and
- "other
".
If either of the following conditions are met:
@@ -101418,19 +101338,14 @@ dictionary EventSourceInit {Set ev's request to request.
Let finalizeEventSourceFetch given response res be to finalize and report
- timing with res, settings's global object, and "other
".
Let processEventSourceEndOfBody given response res be the following step: if - res is not a network error, then finalizeEventSourceFetch - with res, and reestablish the connection.
Fetch request with initiatorType set to "other
" and processResponseEndOfBody set to
processEventSourceEndOfBody and processResponse set
to the following steps given response
@@ -101440,10 +101355,9 @@ dictionary EventSourceInit {
If res is an aborted network error, then fail the connection.
Otherwise, if res is a network error, then call - finalizeEventSourceFetch given res, and reestablish the - connection, unless the user agent knows that to be futile, in which case the user agent - may fail the connection.
Otherwise, if res is a network error, then + reestablish the connection, unless the user agent knows that to be futile, in + which case the user agent may fail the connection.
Otherwise, if res's status is
not 200, or if res's `Content-Type
` is not