- From: Matt Falkenhagen <notifications@github.com>
- Date: Tue, 05 Nov 2019 00:39:46 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/dom/pull/653/review/311569152@github.com>
mattto 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. I've reopened the issue to track this. -- 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_r342435013
Received on Tuesday, 5 November 2019 08:39:48 UTC