Re: [w3c/ServiceWorker] Add Register a Service Worker algorithm for use by other specifications (PR #1848)

@yoshisatoyanagisawa commented on this pull request.



> +
+      : Input
+      :: |storageKey|, a [=/storage key=]
+      :: |scriptURL|, a [=/URL=]
+      :: |scopeURL|, a [=/URL=]
+      :: |workerType|, a [=job/worker type=]
+      :: |updateViaCache|, a [=service worker registration/update via cache mode=]
+      : Output
+      :: none
+
+      1. Set |scriptURL| to the result of running [=Validate and Normalize a Service Worker URL=] with |scriptURL|.
+      1. If |scriptURL| is failure, return.
+      1. Set |scopeURL| to the result of running [=Validate and Normalize a Service Worker URL=] with |scopeURL|.
+      1. If |scopeURL| is failure, return.
+      1. If |scriptURL|'s [=url/origin=] and |scopeURL|'s [=url/origin=] are not [=same origin=], return.
+      1. If the result of running <a>potentially trustworthy origin</a> with |scriptURL|'s [=url/origin=] as the argument is <code>Not Trusted</code>, return.

nit but `Not Trusted` might be `Not Trustworthy`  now upon https://w3c.github.io/webappsec-secure-contexts/#potentially-trustworthy-origin

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/pull/1848#pullrequestreview-5234641021
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/pull/1848/review/5234641021@github.com>