Contact emails
https://groups.google.com/a/chromium.org/g/blink-dev/c/wNOClobsLrs
https://github.com/WICG/sw-launch/blob/main/launch_handler.md
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.
https://github.com/w3ctag/design-reviews/issues/683
Closed. Satisfied to see this move ahead but keeping in mind compatibility with the MiniApp lifecycle.
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 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.
No, this requires browser_tests as it involves managing windows.
chrome://flags/#enable-desktop-pwas-launch-handler
https://bugs.chromium.org/p/chromium/issues/detail?id=955620
https://bugs.chromium.org/p/chromium/issues/detail?id=1222742
https://chromestatus.com/feature/5704553745874944
- Alan Cutter
Flag name
chrome://flags/#enable-desktop-pwas-launch-handler
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
- 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 blink-dev+...@chromium.org.
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.
Hey Alan!Our policy on Origin Trial extensions recently 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, 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.
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
Link to entry on the Chrome Platform Status
Flag name
chrome://flags/#enable-desktop-pwas-launch-handler
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
- 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 blink-dev+unsubscribe@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
+Joyce Toh FYIOn Thu, Apr 28, 2022 at 2:36 AM Alan Cutter <alanc...@chromium.org> wrote:On Wednesday, 27 April 2022 at 8:14:05 pm UTC+10 Yoav Weiss wrote:Hey Alan!Our policy on Origin Trial extensions recently 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, 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, positive dev feedback, TAG approval and crickets on a request for Mozilla position.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.