LGTM3 On Wed, Dec 17, 2025 at 11:32 AM Chris Harrelson <[email protected]> wrote:
> LGTM2, conditioned on filing standards position requests for Mozilla and > Webkit. > > On Wed, Dec 17, 2025 at 8:24 AM Alex Russell <[email protected]> > wrote: > >> LGTM1 with a nit: did y'all ask Mozilla about their position or file a >> position request? Would be good form. >> >> Best, >> >> Alex >> >> On Monday, December 15, 2025 at 9:00:41 AM UTC-8 [email protected] >> wrote: >> >>> Done >>> >>> On Mon, Dec 15, 2025 at 6:39 AM Mike Taylor <[email protected]> >>> wrote: >>> >>>> Hi there, >>>> >>>> Would you mind requesting the privacy, security, debuggability, etc >>>> bits in your chromestatus entry? >>>> >>>> thx >>>> On 12/12/25 1:18 p.m., Chromestatus wrote: >>>> >>>> *Contact emails* >>>> [email protected], [email protected], [email protected] >>>> >>>> *Explainer* >>>> >>>> https://github.com/WICG/manifest-incubations/blob/gh-pages/predictable-app-updating.md >>>> >>>> *Specification* >>>> https://www.w3.org/TR/appmanifest/#updating >>>> >>>> *Summary* >>>> Specify an update eligibility algorithm in the manifest spec. This >>>> makes the update process more deterministic and predictable, giving the dev >>>> more control over whether (and when) updates should apply to existing >>>> installations, and allowing removal of the 'update check throttle' that >>>> user agents currently need to implement to avoid wasting network resources. >>>> >>>> *Blink component* >>>> Blink>AppManifest >>>> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EAppManifest%22> >>>> >>>> *Web Feature ID* >>>> manifest <https://webstatus.dev/features/manifest> >>>> >>>> *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 proposal* >>>> https://www.w3.org/2022/09/13-webapps-minutes.html#t02 >>>> >>>> *Search tags* >>>> pwa <http:///features#tags:pwa>, update <http:///features#tags:update>, >>>> manifest <http:///features#tags:manifest>, manifest update >>>> <http:///features#tags:manifest%20update>, pwa update >>>> <http:///features#tags:pwa%20update> >>>> >>>> *TAG review* >>>> https://github.com/w3ctag/design-reviews/issues/1076 >>>> >>>> *TAG review status* >>>> Issues addressed >>>> >>>> *Risks* >>>> >>>> >>>> *Interoperability and Compatibility* >>>> *No information provided* >>>> >>>> *Gecko*: No signal >>>> >>>> *WebKit*: Positive ( >>>> https://docs.google.com/document/d/1QDqllh8inOcIkTrblERm4HRKYh8Ce9Lu5S7WhOygs_0/edit?tab=t.0#bookmark=id.b76fa6xoh2i9) >>>> Agreement >>>> on update approach with WebKit part of the discussion. >>>> >>>> *Web developers*: Positive ( >>>> https://www.w3.org/2022/09/13-webapps-minutes.html#t02) Discussions at >>>> TPAC 2022 and 2023 involved active discussion with developers, with a >>>> positive consensus. >>>> >>>> *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? >>>> N/A, feature isn't launching on Android. >>>> >>>> >>>> *Debuggability* >>>> *No information provided* >>>> >>>> *Will this feature be supported on all six Blink platforms (Windows, >>>> Mac, Linux, ChromeOS, Android, and Android WebView)?* >>>> No >>>> >>>> *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://flags* >>>> chrome://flags/#enable-web-app-predictable-app-updating >>>> >>>> *Finch feature name* >>>> DesktopPWAsPredictableAppUpdating >>>> >>>> *Rollout plan* >>>> Will ship enabled for all users >>>> >>>> *Requires code in //chrome?* >>>> True >>>> >>>> *Tracking bug* >>>> https://issues.chromium.org/issues/403253129 >>>> >>>> *Launch bug* >>>> https://launch.corp.google.com/launch/4393456 >>>> >>>> *Availability expectation* >>>> Feature is available only in Chrome. >>>> >>>> *Adoption expectation* >>>> This feature paves the way for PWA app migration [1], which is an ask >>>> by both first party and third party vendors as an essential feature for >>>> PWAs (crbug.com/380486617). [1] >>>> https://github.com/WICG/manifest-incubations/blob/gh-pages/pwa-migration-explainer.md >>>> >>>> *Non-OSS dependencies* >>>> >>>> Does the feature depend on any code or APIs outside the Chromium open >>>> source repository and its open-source dependencies to function? >>>> N/A >>>> >>>> *Estimated milestones* >>>> Shipping on desktop 143 >>>> DevTrial on desktop 143 >>>> >>>> *Anticipated spec changes* >>>> >>>> Open questions about a feature may be a source of future web compat or >>>> interop issues. Please list open issues (e.g. links to known github issues >>>> in the project for the feature specification) whose resolution may >>>> introduce web compat/interop risk (e.g., changing to naming or structure of >>>> the API in a non-backward-compatible way). >>>> N/A, anticipated spec changes will not be introducing interop risks. >>>> Changes are being made on Chrome's end to make PWAs more safer. >>>> >>>> *Link to entry on the Chrome Platform Status* >>>> https://chromestatus.com/feature/5148463647686656?gate=5181792593903616 >>>> >>>> *Links to previous Intent discussions* >>>> Intent to Prototype: >>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2B4qT31vY-P2d2e%2Be5F101d_e%2B%3DOEE-%2BnbqxtqHSboeiJFqKOQ%40mail.gmail.com >>>> >>>> >>>> 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 [email protected]. >>>> To view this discussion visit >>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/693c5c6a.050a0220.32a4e5.00be.GAE%40google.com >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/693c5c6a.050a0220.32a4e5.00be.GAE%40google.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> -- >> 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 [email protected]. >> To view this discussion visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/36dd5241-3854-4534-b546-5dd04bb1c140n%40chromium.org >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/36dd5241-3854-4534-b546-5dd04bb1c140n%40chromium.org?utm_medium=email&utm_source=footer> >> . >> > -- > 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 [email protected]. > To view this discussion visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw8y-WohJVL8M%2BWjmyQss3cjgud2gYC8y2WWSTbVmNtARQ%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw8y-WohJVL8M%2BWjmyQss3cjgud2gYC8y2WWSTbVmNtARQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY__MRiORZK%3Ds9gOZ%2B-%2BMVGC78j_ghyDyZZsKn2hvq-QDQ%40mail.gmail.com.
