From 9fb7d7388d7d289ce5581ae4cc21148252467c3a Mon Sep 17 00:00:00 2001 From: Jungkee Song Date: Fri, 24 Aug 2018 04:57:02 -0700 Subject: [PATCH] Rename target client id to replaces client id We had decided to change the name of FetchEvent's targetClientId to replacesClientId to clarify the meaning that this client is a to be replaced client: https://github.com/w3c/ServiceWorker/issues/1091#issuecomment-342569083. Accordingly, this changes the reference to the request's target client id to request's replaces client id. See also: * https://github.com/w3c/ServiceWorker/issues/1245 * https://github.com/w3c/ServiceWorker/pull/1333 * https://github.com/whatwg/fetch/pull/774 --- source | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source b/source index 886bf9e77b2..c253a0f71ec 100644 --- a/source +++ b/source @@ -2836,7 +2836,7 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
  • body
  • client
  • reserved client
    • -
  • target client id
    • +
  • replaces client id
  • initiator
  • destination
  • potential destination
    • @@ -82053,7 +82053,7 @@ interface Location { // but see also url's scheme is a fetch scheme

    Run process a navigate fetch given resource, the source - browsing context, and browsing context, and navigationType.

    + browsing context, and browsingContext, and navigationType.

    Otherwise, resource is a request whose url's scheme @@ -82080,7 +82080,7 @@ interface Location { // but see also navigate", credentials mode to "include", use-URL-credentials flag, redirect mode to "manual", - and target client id to + and replaces client id to browsingContext's active document's relevant settings object's id.