Hi Mike! Yeah, I created the issue to ask if the spec editor can fill out the explainer more https://github.com/w3c/manifest-app-info/issues/57.
For the webkit and gecko signals - commented in the mozilla standard thread. webkit position is tracked in https://bugs.webkit.org/show_bug.cgi?id=222356. I just got a +1 from Aaron on the platform rename issue <https://github.com/w3c/manifest-app-info/issues/55> and will work on submitting pull requests. On Tuesday, August 23, 2022 at 6:18:56 AM UTC-7 mike...@chromium.org wrote: > On 8/22/22 5:40 PM, Ajay Rahatekar wrote: > > +ajayra...@google.com > > On Friday, August 19, 2022 at 7:26:04 AM UTC-7 mike...@chromium.org wrote: > >> On 8/18/22 6:52 PM, Phillis Tang wrote: >> >> Contact emails phi...@chromium.org >> >> Explainer https://github.com/w3c/manifest-app-info/blob/main/explainer.md >> >> One more question: is this correct link? It seems to be a TODO currently. > > >> Specification https://www.w3.org/TR/manifest-app-info >> >> This feature has been shipped on Mobile - see previous status entry >> <https://chromestatus.com/feature/6422599217184768> and I2S >> <https://groups.google.com/a/chromium.org/g/blink-dev/c/neoNUFbEZ8Y/m/7bzJmCWVAQAJ> >> . >> Enabling this on the desktop uses the same "description" and >> "screenshots" fields. >> >> We additionally implemented parsing for the screenshots' "platform >> <https://www.w3.org/TR/manifest-app-info/#platform-member>" member, but >> that was included in the original spec and design. >> >> Summary >> >> Gives developers the ability to add more data (descriptions and >> screenshots) to their PWA install dialog and gives users more insight into >> the apps they are about to install. This implements PWA richer install UI >> on desktop. See previous chromstatus entry for mobile - >> https://chromestatus.com/feature/6422599217184768 >> >> >> Blink component UI>Browser>WebAppInstalls>Desktop >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:UI%3EBrowser%3EWebAppInstalls%3EDesktop> >> >> TAG review https://github.com/w3ctag/design-reviews/issues/30 >> >> TAG review status Issues addressed >> >> Risks >> >> >> Interoperability and Compatibility >> >> *Gecko*: No signal >> >> I see from the mobile I2S that >> https://github.com/mozilla/standards-positions/issues/492 was filed. >> Might be worth pinging that thread and pointing to this I2S, in case >> someone has input. >> >> >> *WebKit*: No signal >> >> Could we file for a signal at >> https://github.com/WebKit/standards-positions/issues? >> >> >> *Web developers*: Positive >> <https://twitter.com/alexey_rodionov/status/1559056724232785921?cxt=HHwWgsCiiZP18KIrAAAA> >> >> *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? >> >> >> Debuggability >> >> Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, Chrome OS, Android, and Android WebView)? Yes >> >> Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >> ? No, there is an open issue for this: >> https://github.com/w3c/manifest-app-info/issues/26 >> >> Flag name chrome://flags/#enable-desktop-pwas-detailed-install-dialog >> >> Requires code in //chrome? Yes >> >> Tracking bug https://crbug.com/1326252 >> >> Launch bug https://crbug.com/1326714 >> >> Estimated milestones >> >> 106 >> >> >> 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). >> https://github.com/w3c/manifest-app-info/issues/55 >> >> Thanks for pointing this out! It would be nice to try to reach consensus >> on this issue before shipping, then maybe needing to immediately >> deprecate/rename the platform member. >> >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/5206272861798400 >> >> 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+...@chromium.org. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABcACaihvDYf47Z%3Dxivbr_NOXgBMW6NbL01av%3D4_FHEA9UXiPw%40mail.gmail.com >> >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABcACaihvDYf47Z%3Dxivbr_NOXgBMW6NbL01av%3D4_FHEA9UXiPw%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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/f54fe89f-296e-46a6-82cc-54ab868622d3n%40chromium.org.
