Should register() trigger an update if only updateViaCache changes?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- documentation, testing, web-dev
Research direction
Start by reading the discussion in pull request #1411 and the WPT case registration-updateviacache.https.html. Determine which register() behavior the project should specify when only updateViaCache changes, including the rejection case; done means the decision is recorded and the specification and test expectations agree.
Written by the indexing model from the issue text.
Description
Spinning off the discussion at https://github.com/w3c/ServiceWorker/pull/1411
The current spec has the following characteristics:
- If register() changes only updateViaCache (not the script url), it triggers a byte-for-byte update check. Therefore it may or may not install a new service worker.
- If the register() promise resolves, the registration takes the new value of updateViaCache. But if it rejects, the value is unchanged. Therefore, updateViaCache may or may not change.
It may be cleaner if updateViaCache is treated as just a setting, and it doesn't itself trigger the byte-for-byte update check. That is, a register() call that changes only updateViaCache will immediately change the property, and resolve.
According to WPT (registration-updateviacache.https.html), Safari and Firefox implement the current spec in that they trigger an update. A test for register() rejecting was just added to that file and I don't know the results yet.
What do people think? @aliams @asutherland @wanderview @youennf @jakearchibald
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
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.
More from w3c/ServiceWorker
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
w3c/ServiceWorker#1391 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
w3c/ServiceWorker#1311 · 1 comment ·
-
apr-2017-f2f
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
w3c/ServiceWorker#1036 · 5 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
w3c/ServiceWorker#1846 ·
-
TPAC2026
Difficulty 3/5 1-2 days Newbie friendliness 35/100
w3c/ServiceWorker#1845 ·
All issues in w3c/ServiceWorker
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bancolombia/sentinel#22 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
objectionary/hone-maven-plugin#1061 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
redhat-developer/rhdh-plugins#4887 · 2 comments ·