Re: [whatwg/dom] Change add/remove event listener behavior for service workers (#653)

annevk commented on this pull request.



> -  <p class="note no-backref">To avoid unnecessary delays, Service Workers [[!SERVICE-WORKERS]]
-  permits skipping event dispatch when no <a>event listeners</a> for the <a>service worker event</a>
-  have been deterministically added in the <a>service worker</a>’s <a for="service worker">set of
-  event types to handle</a> during the very first script evaluation. The <a>event listener</a> in
-  this step will still be added, but the implementations have to inform developers about this
-  behavior.
+  <p>If <var>eventTarget</var> is a {{ServiceWorkerGlobalScope}} object, its
+  <a for="ServiceWorkerGlobalScope">service worker</a>'s
+  <a for="service worker">script resource</a>'s
+  <a for="script resource">has ever been evaluated flag</a> is set, and <var>listener</var>'s
+  <a for="event listener">type</a> matches the {{Event/type}} attribute value of any of the
+  <a>service worker events</a>, then <a>report a warning to the console</a> that this might not give
+  the expected results. [[!SERVICE-WORKERS]]
+
+  <p class="note no-backref">Service workers are only started for event listeners added during the
+  first script evaluation.

Limiting it to `fetch` seems okay, but making it random effectively requires user agents to look at each other's code of sites take a dependency. That's not great.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/pull/653#discussion_r342428457