Re: [w3c/manifest] Specification status report for TPAC 2019 (#782)

A brief rundown of what we talked about at TPAC based on my recollection. Please correct if I messed anything up.

* **Shortcuts (#582)** - Achieved agreement on the format & tacit TAG approval; bug filed with Firefox & Webkit to (potentially) get commitments; @slightlyoff had some interest in bringing back alternate HTTP verb support and params (which we can do later); PR ready for merge. Some discussion around adding a new `rel` value for `link` elements to the Microformats registry for inline declaration of shortcuts (browser interest and UI exposure TBD).
* **File Handling (#626)** - General discussion of file association proposal and agreement on the approach; some questions about what the launch looks like and how the payload is delivered. @marcoscaceres brought up some parallels with drag & drop resolution.
* **`ImageResource`** - Agreed to break out `ImageResource` to a separate spec which would be referenced by Web App Manifest (and other specs). `ImageResource` will be extensible in context to allow for manifest-specific features (and other specs, naturally). Once the new spec is in place, we will migrate `ImageResource` issues to that repo. Agreed to add `description` (#773) and `color_scheme` (#758) members to `ImageResource` upon migration.
* **`beforeInstallPrompt`** - moving this feature to optional (PR inbound: #797)
* **Badging** - Discussed the [badging proposal at WICG](https://github.com/wicg/badging) and came up with [a plan to address badging app icons and tabs/windows independently](https://github.com/WICG/badging/issues/55). Review from @hober was supportive.
* **`allow_list`** - Discussed bringing the concept of [Feature Policy](https://developer.mozilla.org/docs/Web/HTTP/Headers/Feature-Policy)-esque capabilities declaration into the Manifest for auditing, user awareness, etc. @aarongustafson took an action item to write an explainer. (#798)
* **`getInstalledrelatedApps()`** - Agreed to move forward with this
* **[Service Worker Launch Event](https://github.com/WICG/sw-launch)** - General intro/overview & discussion around how launch could allow for better UX in terms of APIs like Share Target, Shortcuts, etc. No action taken (apart from general agreement that it’s worth pursuing).
* **`isInstalled()`** - Into to the idea of a window being able to determine if a PWA for that domain & scope is installed so that it may be launched. Seems to overlap some with `prefer_related_application` (where that app is the PWA), Chrome Apps’ [`url_handlers`](https://developer.chrome.com/apps/manifest/url_handlers), and Windows’ [web-to-app-link concept](https://docs.microsoft.com/en-us/windows/uwp/launch-resume/web-to-app-linking). General agreement that we need to solve this. @raymeskhoury to look for more use cases.
* **Defining "PWA"** - @beverloo brought this up and we agreed to join the current discussion around revising PWA docs on MDN.
* **3D Favicons** - Proposal for spatial icon types for 3D/XR scenarios. We can’t speak to favicons, but we’re cool with adding support in manifest for defining them. `ImageResource` is already set up to handle the MIME  types, but leans on HTML for `sizes` definition. Suggested that the proposal for a third dimension be taken to the WhatWG and, once cleared, we can look to add it into the spec.
* **Screen enumeration** - General walkthrough by Mike W; we like the idea of being able to control window placement.
* **Projections** - [Idea @aarongustafson posted to WICG](https://discourse.wicg.io/t/noodling-on-an-idea-projections-for-web-apps/3900) for enabling apps to advertise widgets, cards, and similar for use in other surfaces (e.g., Live Tiles, Google Now, Samsung Daily, home screen widgets, macOS dashboard widgets, etc.). @beverloo & @slightlyoff working on a similar idea leveraging notification templates. Collaboration & an explainer to come.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/782#issuecomment-533363985