Contact emailsfin...@google.com, dibya...@google.com

Explainer
https://github.com/WICG/manifest-incubations/blob/gh-pages/predictable-app-updating.md

SpecificationNone

Summary

Introduce an `update_token` field and update eligibility algorithm to the
manifest spec. This makes the update process to be more deterministic and
predictable, giving the dev more control over when updates occur, and
allowing removal of 'update check throttle' that user agents currently need
to implement to avoid wasting network resources.


Blink componentBlink>AppManifest
<https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EAppManifest%22>

Motivation

- Consistency: Provide a consistent way to detect when a manifest update
should happen. - Preventing unnecessary user interruption: Users should not
see an update dialog more than necessary to confirm security-sensitive
changes. - User agent flexibility: It should be possible for users agents
to use their judgement to block updates for known bad sites, allow known
trusted apps to update without UX, or allow tiny visual changes to icons
without requiring UX. - Developer control: Developers should have more
control over when the update dialog may show to users. - Reduce network
traffic: Unnecessary network traffic should be minimized.


Initial public proposalTPAC 2022:
https://www.w3.org/2022/09/13-webapps-minutes.html#t02
TPAC 2023: WebApps WG TPAC 2023 Meeting (Day 2)
<https://docs.google.com/document/d/1QDqllh8inOcIkTrblERm4HRKYh8Ce9Lu5S7WhOygs_0/edit?tab=t.0#heading=h.sg3uxnf61udd>

Search tagspwa <https://chromestatus.com/features#tags:pwa>, update
<https://chromestatus.com/features#tags:update>, manifest
<https://chromestatus.com/features#tags:manifest>, manifest update
<https://chromestatus.com/features#tags:manifest%20update>, pwa update
<https://chromestatus.com/features#tags:pwa%20update>

TAG reviewNone

TAG review statusPending

Risks


Interoperability and Compatibility

None


*Gecko*: No signal

*WebKit*: No signal

*Web developers*: No signals

*Other signals*:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that
it has potentially high risk for Android WebView-based applications?

None


Debuggability

None


Is this feature fully tested by web-platform-tests
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
?No

Flag name on about://flagsNone

Finch feature nameNone

Non-finch justificationNone

Requires code in //chrome?True

Tracking bughttps://issues.chromium.org/issues/403253129

Estimated milestones

No milestones specified


Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5148463647686656?gate=5115340859899904

This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2B4qT31vY-P2d2e%2Be5F101d_e%2B%3DOEE-%2BnbqxtqHSboeiJFqKOQ%40mail.gmail.com.

Reply via email to