feat(service-worker): support push subscription changes #61856
Conversation
In this commit, support for `pushsubscriptionchange` events has been added to the service worker Driver. When the push subscription changes, the Driver now captures the event and broadcasts a `PUSH_SUBSCRIPTION_CHANGE` message to clients. This ensures the application is aware of push events and can react accordingly. Unfortunately, it's not possible to perform any end-to-end testing of this feature. The push subscription change event exists in both Blink and Gecko. It is also supported in the latest version of Chrome, which means we can give users the ability to react to this event in order to gather feedback on whether other components might need updates.
|
I see that you just added the If you want your PR to be merged, it has to pass all the CI checks. If you can't get the PR to a green state due to flakes or broken |
|
I see that you just added the If you want your PR to be merged, it has to pass all the CI checks. If you can't get the PR to a green state due to flakes or broken |
|
This PR was merged into the repository by commit 6e1df54. The changes were merged into the following branches: main |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
In this commit, support for
pushsubscriptionchangeevents has been added to the service worker Driver.When the push subscription changes, the Driver now captures the event and broadcasts a
PUSH_SUBSCRIPTION_CHANGEmessage to clients. This ensures the application is aware of push events and can react accordingly.Unfortunately, it's not possible to perform any end-to-end testing of this feature.
The push subscription change event exists in both Blink and Gecko. It is also supported in the latest version of Chrome, which means we can give users the ability to react to this event in order to gather feedback on whether other components might need updates.