Closed Bug 1593310 Opened 3 years ago Closed 2 years ago

Add support for clearing all onboarding impressions in newtab devtools

Categories

(Firefox :: Messaging System, enhancement, P1)

enhancement

Tracking

()

VERIFIED FIXED
Firefox 74
Iteration:
74.1 - Jan 6 - Jan 19
Tracking Status
firefox71 --- wontfix
firefox72 --- wontfix
firefox73 --- wontfix
firefox74 --- verified

People

(Reporter: pdahiya, Assigned: pdahiya)

References

Details

Attachments

(1 file)

  1. Open about:newtab#devtools
  2. Select messages from 'onboarding'
  3. Right now block button is respective to a message

Scope of this bug is to provide 'Reset All' that clears all messageImpressions and providerImpressions inside indexedDB

Assignee: nobody → pdahiya
Iteration: --- → 72.3 - Nov 18 - Dec 1
Priority: -- → P1
Target Milestone: --- → Firefox 72

This is devtool fix that's safe to pick in 73.

Iteration: 72.3 - Nov 18 - Dec 1 → 73.1 - Dec 2 - Dec 15
Priority: P1 → P2
Iteration: 73.1 - Dec 2 - Dec 15 → 73.2 - Dec 16 - Jan 5
Iteration: 73.2 - Dec 16 - Jan 5 → 74.1 - Jan 6 - Jan 19
Priority: P2 → P1

QA Steps

  1. Enable devtools pref and Open about:newtab#devtools
  2. Select messages from 'onboarding'
  3. It should display 'Reset All' button
  4. Click of button should reset impression for all onboarding messages resetting count to 0 impressions
  5. Reset All button should show for all providers except local testing
Pushed by pdahiya@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/de38640b1c7b
Add support for clearing all messages impressions by a provider in newtab devtools r=emcminn
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: Firefox 72 → Firefox 74

I have verified that the "Reset all" button was added in about:newtab#devtools page for all providers, except local testing, and works by clearing all impressions for selected provider (I was able to check only for "cfr" provider), using Firefox Nightly 74.0a1 (Build ID 20200209215935) on 10 x64, Mac 10.14 and Linux Ubuntu 16.04.

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.