WICG / web-app-launch

Web App Launch Handler
Other
74 stars 31 forks source link

"existing-client-retain" does not work but "existing-client" does #55

Closed giraffepoo closed 2 years ago

giraffepoo commented 2 years ago

musicrerror

The current demo app under https://web.dev/launch-handler/ does not work as the error above is shown. I looked through chromium bugs list to find that "existing-client" works and I confirmed it with my browser.

Is there going to be a release soon for "existing-client-retain"? (Sorry I'm very new to PWA feature dev - asking as this is a feature I heavily need for current project)

alancutter commented 2 years ago

The implementation is coming, in the meantime use both for backwards compat:

"launch_hander": {
  "route_to": ["existing-client-retain", "existing-client"],
  "navigate_existing_client": "never"
}
alancutter commented 2 years ago

Old browsers will ignore any unknown enum values in the "route_to" list until they find one they can parse.

Stefaans commented 2 years ago

The implementation is coming, in the meantime use both for backwards compat:

"launch_hander": {
  "route_to": ["existing-client-retain", "existing-client"],
  "navigate_existing_client": "never"
}

Typo in "launch_handler" and wondering if you meant "navigate_new_clients" instead of "navigate_existing_client"? In other words:

"launch_handler": {
"route_to": [ "existing-client-retain", "existing-client" ],
"navigate_new_clients": "never"
},
alancutter commented 2 years ago

Ty for typo spotting.

There was no navigate_new_clients field, only navigate_existing_client. New clients always navigate otherwise they'd be about:blank.