For the 3 review categories in chromestatus (security, privacy, and debuggability), I have clicked on request review but have not found a way to post comments from the UI.
For security and privacy, we have a self-review at: manifest-incubations/scope_extensions-security-privacy-questionnaire.md at gh-pages · WICG/manifest-incubations (github.com) <https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-security-privacy-questionnaire.md> For debuggability, here are the survey responses until I find out how to add to the comments at chromestatus: (1) Does the introduction of the new Web Platform feature break Chrome DevTools' existing developer experience? No. (2) Does Chrome DevTools' existing set of tooling features interact with the new Web Platform feature in an expected way? Yes. (3) Would the new Web Platform feature's acceptance and/or adoption benefit from adding a new developer workflow to Chrome DevTools? Yes. If adopted, this new feature would benefit from new UI and tooling in the Application Page of Chrome DevTools. DevTools support can help developers determine if they have set up the web app association configuration correctly and if their specified scope_extensions are valid. On Wednesday, October 11, 2023 at 2:12:09 PM UTC-7 Lu Huang wrote: > We would like to start running this experiment from 120 through 123 > inclusive, but may have to delay start to 121 running through 124. > > > > On Wednesday, October 11, 2023 at 7:54:51 AM UTC-7 Chris Harrelson wrote: > >> Please also fill out the 3 other review categories (security, privacy, >> debuggability) in chromestatus. >> >> >> On Wed, Oct 11, 2023 at 7:13 AM Mike Taylor <mike...@chromium.org> wrote: >> >>> Hi there, >>> >>> Could you clarify which milestones you would like to run the experiment >>> on? >>> >>> thanks, >>> Mike >>> On 10/11/23 6:05 AM, 'Lu Huang' via blink-dev wrote: >>> >>> Contact emails >>> lu...@microsoft.com, luig...@microsoft.com, alanc...@chromium.org >>> >>> Explainer >>> >>> https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md >>> >>> Specification >>> None >>> >>> Design docs >>> >>> https://docs.google.com/document/d/1-idhx8heajbPYl3cdXFVCjpIuf96cRa_DrRk6147ELI/edit?usp=sharing >>> >>> Summary >>> >>> Adds a "scope_extensions" app manifest member that enables web apps to >>> extend their scope to other origins. Example usage: { "name": "Example", >>> "display": "standalone", "start_url": "/index.html", "scope_extensions": [ >>> {"origin": "https://*.example.com"}, {"origin": "https://example.co.uk"; >>> <https://example.co.uk>}, {"origin": "https://*.example.co.uk"} ] } >>> This allows sites that control multiple subdomains and top level domains to >>> be presented as a single web app. Requires listed origins to confirm >>> association with the web app using a .well-known/web-app-origin-association >>> configuration file. { "web_apps" : [ {"web_app_identity": >>> "https://sample-app.com/"; <https://sample-app.com/>} ] } >>> >>> >>> Blink component >>> UI>Browser>WebAppInstalls >>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:UI%3EBrowser%3EWebAppInstalls> >>> >>> TAG review >>> https://github.com/w3ctag/design-reviews/issues/875 >>> >>> TAG review status >>> Pending >>> >>> Risks >>> >>> Interoperability and Compatibility >>> *Gecko*: No signal ( >>> https://github.com/mozilla/standards-positions/issues/904) >>> >>> *WebKit*: No signal ( >>> https://github.com/WebKit/standards-positions/issues/265) >>> >>> *Web developers*: No signals >>> >>> *Other signals*: >>> >>> Ergonomics >>> >>> None. >>> >>> >>> Activation >>> >>> None. >>> >>> >>> 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? >>> >>> >>> Goals for experimentationAllow app partners to experiment more broadly >>> with the scope_extensions feature and provide feedback. We want to evaluate >>> the shape of the scope_extensions API for ease of use and expose any corner >>> cases. Specifically, we want to understand if origin-level granularity is >>> sufficient without path filters. We will evaluate this based on feedback >>> from OT participants. >>> >>> Ongoing technical constraints >>> >>> None. >>> >>> >>> Debuggability >>> >>> DevTools Application pane will be the appropriate surface to add >>> debugging support. Specifically, a section can be added to help >>> troubleshoot the status of origin association validation. Additionally, >>> edge://web-app-internals/ also have relevant information for debugging. >>> >>> >>> Will this feature be supported on all six Blink platforms (Windows, Mac, >>> Linux, Chrome OS, Android, and Android WebView)?No >>> >>> Supported on Windows, MacOS, Linux, ChromeOS. Not supported on mobile >>> platforms where app identity is implemented differently. >>> >>> >>> 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 chrome://flags >>> about://flags/#enable-desktop-pwas-scope-extensions >>> >>> Finch feature name >>> None >>> >>> Non-finch justification >>> None >>> >>> Requires code in //chrome? >>> False >>> >>> Tracking bug >>> https://bugs.chromium.org/p/chromium/issues/detail?id=1250011 >>> >>> Estimated milestones >>> Dev Trial - 115 >>> Origin Trial 120 or 121 >>> >>> >>> *Link to entry on the Chrome Platform Status * >>> https://chromestatus.com/feature/5746537956114432 >>> >>> Links to previous Intent discussions >>> Intent to prototype: >>> https://groups.google.com/a/chromium.org/g/blink-dev/c/-iySPmw8o34/m/oLgrCUQXAQAJ >>> >>> Ready for Trial: >>> https://groups.google.com/a/chromium.org/g/blink-dev/c/OBZBZwS6qr0/m/VRySwd40AQAJ >>> >>> >>> 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/37136c0f-1f17-4da1-9398-b8ba890d2ee2n%40chromium.org >>> >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/37136c0f-1f17-4da1-9398-b8ba890d2ee2n%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 blink-dev+...@chromium.org. >>> >> To view this discussion on the web visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/52dd7f02-9ccc-4b57-9293-a9d1450bbbd5%40chromium.org >>> >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/52dd7f02-9ccc-4b57-9293-a9d1450bbbd5%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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d81efcbf-9396-4d52-ba8f-a4d7eec302fcn%40chromium.org.
