Skip to content

Include path in web push payload for backwards compatibility#2614

Merged
rosa merged 1 commit intomainfrom
backwards-compatible-web-push-payload
Feb 25, 2026
Merged

Include path in web push payload for backwards compatibility#2614
rosa merged 1 commit intomainfrom
backwards-compatible-web-push-payload

Conversation

@rosa
Copy link
Member

@rosa rosa commented Feb 25, 2026

This is a quick follow-up to #2511, that I realised just as I clicked on merge 😅 (luckily before deploying anything).

Old service workers cached in browsers still read data.path from the push notification payload. Include it alongside data.url so notification clicks keep working until those service workers update.

Currently we only register the service worker in the notification settings screen, so this won't happen very often. Once we introduce offline mode, we'll register the service worker in more places, so we should be able to remove this.

Old service workers cached in browsers still read `data.path` from the
push notification payload. Include it alongside `data.url` so notification
clicks keep working until those service workers update.

Currently we only register the service worker in the notification
settings screen, so this won't happen very often. Once we introduce
offline mode, we'll register the service worker in more places, so we
should be able to remove this.
@rosa rosa merged commit fc0e477 into main Feb 25, 2026
12 checks passed
@rosa rosa deleted the backwards-compatible-web-push-payload branch February 25, 2026 19:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant