LGTM to extend experimentation to M103 On Thu, Apr 28, 2022 at 5:44 PM Ibrahim Karahan <[email protected]> wrote:
> +Joyce Toh <[email protected]> FYI > > On Thu, Apr 28, 2022 at 2:36 AM Alan Cutter <[email protected]> > wrote: > >> >> >> On Wednesday, 27 April 2022 at 8:14:05 pm UTC+10 Yoav Weiss wrote: >> >>> Hey Alan! >>> >>> Our policy >>> <https://www.chromium.org/blink/launching-features/#step-3-optional-origin-trial> >>> on Origin Trial extensions recently >>> <https://groups.google.com/a/chromium.org/g/blink-api-owners-discuss/c/Jzij3fKN5kA/m/Irt_B2DmCQAJ> >>> changed, and we now require to see significant progress on various >>> shipping-related work before approving extensions (for 3 milestones at a >>> time). >>> Have y'all started working on a spec, signal requests >>> <https://bit.ly/blink-signals>, WPTs, etc? >>> >>> Since the policy change is recent, we may be able to provide affordances >>> (e.g. a 1 milestone extension) to enable you to catch up on such work if >>> you haven't done that yet. >>> >> >> Oof, wasn't expecting this. Thanks for the helpful links, I've >> reprioritised my immediate workload to have this spec progress happen >> sooner. The 1 milestone extension would be appreciated in the meantime. >> So far all I have is an explainer >> <https://github.com/WICG/sw-launch/blob/main/launch_handler.md>, positive >> dev feedback >> <https://docs.google.com/document/d/1t60YeQ-d-FSr9i91jvylW6sA7_R4jDnX1G4_PDfssYE/edit>, >> TAG approval >> <https://github.com/w3ctag/design-reviews/issues/683#issuecomment-1088481698> >> and >> crickets on a request for Mozilla position >> <https://github.com/mozilla/standards-positions/issues/567>. >> I will spin up on getting a draft spec written (re-requesting a spec >> mentor as my existing one went on extended leave) and reach out for more >> feedback from the spec community. >> > Thanks for prioritizing this work! :) > >> >>> >>> Aside: It seems like this thread was not picked up by our tooling due to >>> using the wrong title ("Request" rather than "Intent") and a mismatched >>> Chrome Status entry. >>> /cc +Jason Robbins <[email protected]> >>> >> >> My bad; the dangers of copy paste. D: >> I wasn't able to find a clean template on chromestatus.com but I might >> be holding the tool wrong. >> >> Corrected version: >> >> *Tracking bugs* >> https://bugs.chromium.org/p/chromium/issues/detail?id=1231886 >> https://bugs.chromium.org/p/chromium/issues/detail?id=1247817 >> >> >> *Link to entry on the Chrome Platform Status* >> https://www.chromestatus.com/feature/5722383233056768 >> >> >>> >>> On Tue, Apr 26, 2022 at 5:18 AM 'Alan Cutter' via blink-dev < >>> [email protected]> wrote: >>> >>>> Contact emails >>>> >>>> [email protected] >>>> >>>> Original I2E >>>> >>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/wNOClobsLrs >>>> >>>> Explainer >>>> >>>> https://github.com/WICG/sw-launch/blob/main/launch_handler.md >>>> >>>> Summary >>>> >>>> Adds a "launch_handler" app manifest member that enables web apps to >>>> customise their launch behaviour across all types of app launch >>>> triggers (start menu launch, link capture, share target, etc.). Example >>>> usage: { "name": "Example app", "start_url": "/index.html", >>>> "launch_handler": { "route_to": "existing-client-navigate" } } This >>>> will cause all launches of the Example app to focus an existing app window >>>> and navigate it (if it exists) instead of always launching a new app >>>> window. >>>> >>>> >>>> Blink component >>>> >>>> Blink>AppManifest >>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EAppManifest> >>>> >>>> TAG review >>>> >>>> https://github.com/w3ctag/design-reviews/issues/683 >>>> >>>> TAG review status >>>> >>>> Closed. Satisfied to see this move ahead but keeping in mind >>>> compatibility with the MiniApp lifecycle >>>> <https://github.com/WICG/sw-launch/issues/52>. >>>> >>>> >>>> Risks:Interoperability and CompatibilityGecko: No signal >>>> <https://github.com/mozilla/standards-positions/issues/567> >>>> Web developers: Strong positive signals on the previous Declarative >>>> Link Capturing origin trial >>>> <https://developer.chrome.com/origintrials/#/view_trial/4285175045443026945>, >>>> strong positive signals from the origin trial so far >>>> <https://docs.google.com/document/d/1t60YeQ-d-FSr9i91jvylW6sA7_R4jDnX1G4_PDfssYE/edit#> >>>> . >>>> >>>> Experiment Summary >>>> >>>> >>>> https://docs.google.com/document/d/1t60YeQ-d-FSr9i91jvylW6sA7_R4jDnX1G4_PDfssYE/edit?usp=sharing >>>> >>>> >>>> Experiment Goals >>>> >>>> - Test the new syntax with "existing_client_navigate" removed. >>>> >>>> - Give more opportunities to gather feedback on the "route_to": >>>> "existing-client-retain" behaviour that wasn't present in the DLC origin >>>> trial. >>>> >>>> >>>> Experiment Timeline >>>> >>>> Previous: M97 to M102. >>>> >>>> Requested: M103 to M108. >>>> >>>> Reason this experiment is being extended >>>> >>>> The shape of the API changed >>>> <https://github.com/WICG/sw-launch/pull/53> to address TAG feedback on >>>> default behaviours. >>>> >>>> Will this feature be supported on all six Blink platforms (Windows, >>>> Mac, Linux, Chrome OS, Android, and Android WebView)? >>>> >>>> No, desktop only. >>>> >>>> Is this feature fully tested by web-platform-tests >>>> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> >>>> ? >>>> >>>> No, this requires browser_tests >>>> <https://source.chromium.org/search?q=class:WebAppLaunchHanderBrowserTest&ss=chromium> >>>> as it involves managing windows. >>>> >>> Have you tried testing this with TestDriver >>> <https://web-platform-tests.org/writing-tests/testdriver.html>? If >>> that's not possible, it may be interesting to file bugs to enable the >>> missing functionality. >>> >> >> Thanks for the pointer, this doesn't have the capabilities for testing >> this behaviour. I've filed >> https://github.com/web-platform-tests/wpt/issues/33835 to see if they >> think it's viable. >> >>> >>>> Flag name >>>> >>>> chrome://flags/#enable-desktop-pwas-launch-handler >>>> >>>> kWebAppEnableLaunchHandler >>>> <https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/public/common/features.h;bpv=1;bpt=1;l=376?q=kWebAppEnableLaunchHandler&gsn=kWebAppEnableLaunchHandler&gs=kythe%3A%2F%2Fchromium.googlesource.com%2Fchromium%2Fsrc%3Flang%3Dc%252B%252B%3Fpath%3Dthird_party%2Fblink%2Fpublic%2Fcommon%2Ffeatures.h%23dBeGhIBrlUn9xqyup36XrW7qdqyxtZdxlPtCpwHSK7k> >>>> >>>> >>>> Tracking bug >>>> >>>> https://bugs.chromium.org/p/chromium/issues/detail?id=955620 >>>> >>>> https://bugs.chromium.org/p/chromium/issues/detail?id=1222742 >>>> >>>> Link to entry on the Chrome Platform Status >>>> >>>> https://chromestatus.com/feature/5704553745874944 >>>> >>>> >>>> Previous blink-dev threads >>>> Intent to Prototype >>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/8tNe2jrJ78A> >>>> Intent to Experiment >>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/wNOClobsLrs> >>>> >>>> >>>> >>>> - Alan Cutter >>>> >>>> -- >>>> 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 on the web visit >>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANJJ2CkdQUQVvgo81PCPf%2BqpZ9VubW_c%2BVpB1nAoZz4u63Arfw%40mail.gmail.com >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANJJ2CkdQUQVvgo81PCPf%2BqpZ9VubW_c%2BVpB1nAoZz4u63Arfw%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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfWV2tyv1ntD4YwF%3DT5%3DN1%2B8VfD7eOPs66DrHMRBan9LBA%40mail.gmail.com.
