Update collection dismiss pref default
Categories
(Firefox :: New Tab Page, enhancement, P1)
Tracking
()
People
(Reporter: thecount, Assigned: thecount)
References
Details
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
|
Details | Review |
We want to update the default value of browser.newtabpage.activity-stream.discoverystream.isCollectionDismissible from false to true.
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
To Test:
- Set browser.newtabpage.activity-stream.discoverystream.endpoints to http,https
- Set browser.newtabpage.activity-stream.discoverystream.config to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://e5e8374d-fffa-4a77-a604-31603852b6fd.mock.pstmn.io/collectiontest"}
Expected, you should see a collection in the top row of newtab with a dismiss button.
If you're outside the US, you also need to set this pref: browser.newtabpage.activity-stream.discoverystream.spocs-endpoint to https://spocs.getpocket.com/spocs?site=1123212®ion=CA&country=US
This pref is read here: https://searchfox.org/mozilla-central/source/browser/components/newtab/common/Reducers.jsm#789
This sets some state, which in turn sets this inside a react component: browser
Updated•4 years ago
|
Assignee | ||
Comment 3•4 years ago
•
|
||
To test with more than three items, for now, use these steps:
- Set browser.search.region to US.
- Set browser.newtabpage.activity-stream.discoverystream.endpoints to http,https.
- Set browser.newtabpage.activity-stream.discoverystream.config to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://e5e8374d-fffa-4a77-a604-31603852b6fd.mock.pstmn.io/1615081-layout"}
Pushed by sdowne@getpocket.com: https://hg.mozilla.org/integration/autoland/rev/c3b6e1ef06b4 Update default pref for collection dismiss r=Mardak
Comment 5•4 years ago
|
||
bugherder |
Comment 6•4 years ago
|
||
This issue was part of the work done for [PI-643] Staged Rollout: activity-stream story collection dismiss pref that was signed off as GREEN. Considering this I am marking this issue as VERIFIED.
Assignee | ||
Comment 7•4 years ago
|
||
[Tracking Requested - why for this release]: We're good flipping this on in beta too. This means the flip hits release sooner.
Right now there is a rollout for this value to flip, we're confident in it and are moving it to true for all channels.
Assignee | ||
Comment 8•4 years ago
|
||
Comment on attachment 9153210 [details]
Bug 1642436 - Update default pref for collection dismiss
Beta/Release Uplift Approval Request
- User impact if declined: User experience for collections impacted by not being able to be dismissed.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: To Test:
- Set browser.newtabpage.activity-stream.discoverystream.endpoints to http,https
- Set browser.newtabpage.activity-stream.discoverystream.config to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://e5e8374d-fffa-4a77-a604-31603852b6fd.mock.pstmn.io/collectiontest"}
Expected, you should see a collection in the top row of newtab with a dismiss button.
If you're outside the US, you also need to set this pref: browser.newtabpage.activity-stream.discoverystream.spocs-endpoint to https://spocs.getpocket.com/spocs?site=1123212®ion=CA&country=US
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): It's a 1 line pref flip for a pref that's been tested with a normandy study previously, and is currently on via rollout in release.
- String changes made/needed: none
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 10•4 years ago
|
||
The rollout in bug 1642682 seems to be limited to en-US builds. What's the effect for this on localized builds, whether inside or outside the US?
Updated•4 years ago
|
Assignee | ||
Comment 11•4 years ago
|
||
This pref is fine to be on globally.
It augments an existing feature (collections) that, has separate controls on a per locale basis. (the value in the content and if spocs are enabled)
Spocs are currently enabled in US only right now, and the collections content is only available for US too. If either of those two are false, this pref is ignored.
When we enable collections for other regions or locales, we would want the value in this pref to be the same for all locales, for the foreseeable future.
Comment 12•4 years ago
|
||
Comment on attachment 9153210 [details]
Bug 1642436 - Update default pref for collection dismiss
approved for 78.0b5
Comment 13•4 years ago
|
||
bugherder uplift |
Description
•