| Summary: | notificationClick openWindow goes to PWA root instead of url given | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Mark R <mark.romano> |
| Component: | WebKit API | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Major | CC: | beidson, bfulgham, conner, rniwa, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 17 | ||
| Hardware: | iPhone / iPad | ||
| OS: | iOS 17 | ||
|
Description
Mark R
2023-10-25 15:08:56 PDT
We have determined that it is actually the call to matchingClient.navigate(destinationUrl) that is failing with "TypeError: navigate failed" There are no windows open for the service worker, the PWA has been closed, and so has Safari. Are there any updates on why this isn't working properly? As you can see in my snippet, we have a notificationclick message that can have a URL in it. Basically we want to focus and navigate (or openWindow to the url if no client found). It seems pretty straightforward, but users variably see different behaviors - sometimes the app is focused but doesn't navigate, sometimes the app doesn't even focus. Is there a specific pattern to follow in a notificationclick event handler such that focus/navigate/openWindow always works on ios? This is a regression (i.e. used to work on some versions of iOS)?f Are there any updates on this? |