We discussed this, and we'd like to split onEngegament in: onEngagement, onAbandonment, onImpression, where onImpression won't happen for the "impression" event, but will rather stick to the telemetry definition (result visible when engagement or abandonment happen).
Bug 1857236 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We discussed this, and we'd like to split onEngegament in: onEngagement, onAbandonment, onImpression, where onImpression won't happen for the "impression" event, but will rather stick to the telemetry definition (result visible when engagement or abandonment happen).
Each provider will declare which notifications it wants to handle through something like:
```
get notifications() {
return ["abandonment", "engagement", "impression", ...];
}
```
We discussed this, and we'd like to split onEngegament in: onEngagement, onAbandonment, onImpression, where onImpression won't happen for the "impression" event (we should rename it to "pause" event or such), but will rather stick to the telemetry definition (result visible when engagement or abandonment happen).
Each provider will declare which notifications it wants to handle through something like:
```
get notifications() {
return ["abandonment", "engagement", "impression", ...];
}
```