Spec additional Client API features in V2
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
We decided to not expose reserved client that closed #1228 #1215 #1123 #1078 #1035 #1034 #1031 #1030.
For V1,
Remove:
-
Client.reserved. -
ClientQueryOptions.includeReserved. -
FetchEvent.reservedClientId. -
FetchEvent.targetClientId. -
FetchEventInit.reservedClientId. -
FetchEventInit.targetClientId.
Do:
- Clean up the steps of
Clientsinterface methods.
For V2,
Spec:
-
FetchEvent.resultingClientId,FetchEvent.replacesClientId, and the underlying behavior including the execusion ready flag as discussed in https://github.com/w3c/ServiceWorker/issues/1091#issuecomment-342569083. - Clean up the steps of
Clientsinterface methods including makingclients.get()resolves when the client is execution ready; making sureclients.claim()algorithm to not claim reserved clients.
EDIT: Change the name of FetchEvent.targetClientId (for V2) to FetchEvent.replacesClientId as per https://github.com/w3c/ServiceWorker/issues/1091#issuecomment-342569083.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the V1 and V2 checklists in this issue, then read the linked discussion in ServiceWorker issue #1091 and the referenced reserved-client issues. The work is done when the Clients method algorithms and the V2 FetchEvent fields, execution-ready behavior, and claim rules are fully specified.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100