We surely want to change it, either remove or rename it to "pause" and make the pause longer than 1s, so it's more meaningful. Though at this time there's no plan from DS or Product to use those pause measurements, so we'd better just remove it, and reintroduce a new event when necessary. As a side note, we're also slightly modifying the Abandonment event, that currently only tracks blurring the Address Bar, so that it will also happen when the search context changes (e.g. on Tab Switch, even if the address bar remains focused, we should count an abandonment because the search terms are fully replaces). As a consequence that will make impressions a bit more frequent, but more consistent. we'll also add a `reason` property to the abandonment event. I just posted an update to https://mozilla-hub.atlassian.net/browse/SNG-1172
Bug 1878983 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 surely want to change it, either remove or rename it to "pause" and make the pause longer than 1s, so it's more meaningful. Though at this time there's no plan from DS or Product to use those pause measurements, so we'd better just remove it, and reintroduce a new event when necessary. As a side note, we're also slightly modifying the Abandonment event, that currently only tracks blurring the Address Bar, so that it will also happen when the search context changes (e.g. on Tab Switch, even if the address bar remains focused, we should count an abandonment because the search terms are fully replaced). As a consequence that will make impressions a bit more frequent, but more consistent. we'll also add a `reason` property to the abandonment event. I just posted an update to https://mozilla-hub.atlassian.net/browse/SNG-1172