Closed
Bug 1482113
Opened 6 years ago
Closed 6 years ago
Don't collect metrics when previewing Snippets
Categories
(Firefox :: Messaging System, enhancement, P2)
Firefox
Messaging System
Tracking
()
People
(Reporter: giorgos, Assigned: rrosario)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
When previewing Snippets in AS Router we shouldn't collect any snippet related metrics (impression, click, etc).
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Severity: normal → enhancement
Priority: P3 → P2
Updated•6 years ago
|
Priority: P2 → P3
Updated•6 years ago
|
Iteration: 63.5 - Sep 3 → 64.2 (Sep 28)
Updated•6 years ago
|
Priority: P3 → P2
Assignee | ||
Comment 1•6 years ago
|
||
To clarify, this is about previewing snippets using the about:newtab?endpoint=URL mechanism. *grabs*
Assignee: nobody → rrosario
Comment 2•6 years ago
|
||
Comment 3•6 years ago
|
||
Commit pushed to master at https://github.com/mozilla/activity-stream
https://github.com/mozilla/activity-stream/commit/0db5021394d946812f25e1c4754af9978bef9b71
Fix Bug 1482113 - Don't collect metrics when previewing Snippets (#4431)
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Comment 4•6 years ago
|
||
status-firefox64:
--- → fixed
Target Milestone: --- → Firefox 64
Comment 5•6 years ago
|
||
I've changed the
browser.newtabpage.activity-stream.asrouter.messageProviders
pref to
[{"id":"onboarding","type":"local","localProvider":"OnboardingMessageProvider","enabled":false,"cohort":0},{"id":"snippets","type":"remote","url":"https://snippets.cdn.mozilla.net/%STARTPAGE_VERSION%/%NAME%/%VERSION%/%APPBUILDID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/","updateCycleInMs":14400000,"enabled":true},{"id":"cfr","type":"local","localProvider":"CFRMessageProvider","enabled":true,"cohort":"nightly"}]
which enabled snippets while I am on about:newtab#asrouter, but any action I take on the snippet is still considered valid. Which leads me to believe that I'm looking in the wrong place.
@Ricky, is there any other way I can verify this issue?
Flags: needinfo?(rrosario)
Assignee | ||
Comment 6•6 years ago
|
||
Sent the info on slack.
Testing doc:
https://docs.google.com/document/d/1rJXREddGUx0F7J3sseQbYXY_tkW4wL1CEyaxbRbn-pg/edit
in order to test this, you can follow the same steps in the document but instead whitelist `gist.githubusercontent.com` and use this endpoint https://gist.githubusercontent.com/piatra/70234f08696c0a0509d7ba5568cd830f/raw/41338334ba7e523020b0ea9a875f872ccb050633/messages.json
Flags: needinfo?(rrosario)
Comment 7•6 years ago
|
||
Thanks again Ricky for your help with this.
I have verified that the issue is no longer reproducible on the latest Nightly 64.0a1 (Build ID 20180927100044) on Windows 10 x64, Mac 10.13.3, and Arch Linux x64.
Status: RESOLVED → VERIFIED
Comment 8•6 years ago
|
||
The status for 63 was set to affected by the AS team - is this something we intend to request approval on or is it riding the trains?
Flags: needinfo?(rrosario)
QA Contact: tspurway
Assignee | ||
Comment 9•6 years ago
|
||
Oh I see. This isn't worth uplifting. Let it ride the choo choo
Flags: needinfo?(rrosario)
Updated•6 years ago
|
QA Contact: tspurway
Updated•5 years ago
|
Component: Activity Streams: Newtab → Messaging System
You need to log in
before you can comment on or make changes to this bug.
Description
•