Re: [w3c/ServiceWorker] Editorial: Queue a task to resolve/reject promise or when fire an event. (PR #1755)

monica-ch left a comment (w3c/ServiceWorker#1755)

Thanks @yoshisatoyanagisawa for the thorough review, and thanks @domenic for the
[threading-model write-up](https://github.com/w3c/ServiceWorker/pull/1755#issuecomment-2661840247)
— that framing is really helpful.

I've just rebased this PR onto the latest `main`. Following Domenic's guidance
that *"it is totally fine if only item 1 on this list gets done"*, I'd like to
keep this PR scoped to **item 1** (queuing tasks for promise resolution / event
firing per #1740) and split out the larger parallel-queue work into follow-ups.

Proposed plan:

- **This PR (#1755):** land the task-queuing fixes as-is
- **NavigationPreloadManager:** reading a boolean flag is atomic (per your own
  follow-up conclusion) — I can add a short editorial note here, or defer.
  Preference?
- **Clients API — dedicated parallel queue:** file as follow-up (Domenic's item 4)
- **Cache / CacheStorage — dedicated parallel queue:** file as follow-up
  (Domenic's item 4; also related to #1740 and #1831)
- **Appendix A "in parallel" annotations:** file as follow-up (Domenic's item 2;
  umbrella #1172)

Per @gterzian's suggestion, I'll also mirror Domenic's write-up into #1172 so
it survives this PR and can be referenced from the follow-ups.

If this split works for you, I'll file the follow-ups and address the remaining
in-scope comments here.

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

Message ID: <w3c/ServiceWorker/pull/1755/c4963401716@github.com>