Add a capability that lets us set different defaults for top sites and top stories during the first 48 hours of the default profile's lifetime
Categories
(Firefox :: New Tab Page, task)
Tracking
()
People
(Reporter: mconley, Assigned: mconley)
References
(Blocks 2 open bugs, )
Details
(Whiteboard: [hnt])
Attachments
(9 files, 2 obsolete files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-release+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-release+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-release+
|
Details | Review |
During the first 48 hours of the default profile lifetime (so this shouldn't impact new selectable profiles), we want to be able to experiment with setting the default pref values for top sites and top stories enablement to false. Users should still be able to pref those on during that 48 hour period.
After the 48 hour period, we should change the defaults back (but ensure that if the user had expressed a preference to enable OR disable those sections during the 48 hour period, that we respect that).
The transition after 48 hours should not wait until the next restart - we should be checking every time the user opens a new tab if they were previously in the 48 hour window to see if we should transition out of that state.
This experimental capability will default to using 48 hours as our threshold, but we want to be able to adjust that if need be via Nimbus.
We also need the ability to show a message to users after having transitioned out of that state - for example "hey, we turned these things on now that you've had a chance to get used to the browser. Here's how you can control them".
| Assignee | ||
Comment 1•2 months ago
|
||
| Assignee | ||
Comment 2•2 months ago
|
||
| Assignee | ||
Comment 3•2 months ago
|
||
| Assignee | ||
Comment 4•2 months ago
|
||
Updated•2 months ago
|
Updated•2 months ago
|
| Assignee | ||
Comment 5•2 months ago
|
||
This is so that if there are any other feeds that want to emit actions on initialization
that the StartupCacheInit feed should hear about, it will be initialized and be able
to hear about them.
This is needed for the PrefsFeed activation window check, which might emit actions on
initialization that a cached page should hear about.
Updated•2 months ago
|
Updated•2 months ago
|
| Assignee | ||
Updated•2 months ago
|
Updated•2 months ago
|
| Assignee | ||
Updated•2 months ago
|
Backed out for causing bcv failures.
Comment 10•2 months ago
|
||
Comment 11•2 months ago
|
||
Backed out for causing Talos failures.
Backout link: https://hg.mozilla.org/integration/autoland/rev/d5945bcd5811
Failure log:
https://treeherder.mozilla.org/logviewer?job_id=545045010&repo=autoland&task=Ph04EsSYT72i8KmLsK1Uuw.0&lineNumber=1629
https://treeherder.mozilla.org/logviewer?job_id=545018154&repo=autoland&task=fjxz8sYaRNq4JCk7x1cPHw.0&lineNumber=1092
Comment 12•2 months ago
|
||
Comment 13•2 months ago
|
||
| bugherder | ||
| Assignee | ||
Comment 14•2 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D279335
Updated•2 months ago
|
| Assignee | ||
Comment 15•2 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D279336
Updated•2 months ago
|
| Assignee | ||
Comment 16•2 months ago
|
||
This is so that if there are any other feeds that want to emit actions on initialization
that the StartupCacheInit feed should hear about, it will be initialized and be able
to hear about them.
This is needed for the PrefsFeed activation window check, which might emit actions on
initialization that a cached page should hear about.
Original Revision: https://phabricator.services.mozilla.com/D279362
Updated•2 months ago
|
Comment 17•2 months ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined: None, but the growth team will be unable to do experiments related to the newtab 48 hour activation window on the release channel unless this foundational code lands.
- Code covered by automated testing: yes
- Fix verified in Nightly: no
- Needs manual QE test: no
- Steps to reproduce for manual QE testing:
- Risk associated with taking this patch: low
- Explanation of risk level: This has been on Nightly for a few days now, and is mostly just plumbing the creation date of the profile down into the newtab code, so it's fairly well understood.
- String changes made/needed: None.
- Is Android affected?: no
Comment 18•2 months ago
|
||
:mconley, could part 4 be tracked under a different bug?
I'll take part 1 - 3 for beta, but it's harder to track uplifts when a patch lands later under the same bug.
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Comment 19•2 months ago
|
||
| uplift | ||
Updated•2 months ago
|
| Assignee | ||
Comment 20•2 months ago
|
||
Having the 4th part kinda dangling out here is making things hard to track for RelMan, so I'm going to close this one out and do part 4 in a separate bug.
Comment 21•2 months ago
|
||
Comment on attachment 9538199 [details]
Bug 2009017 - Part 4: Add support for newtab activation window experiments. r?#home-newtab-reviewers!
Revision D279337 was moved to bug 2013416. Setting attachment 9538199 [details] to obsolete.
| Assignee | ||
Comment 22•2 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D279335
Updated•2 months ago
|
| Assignee | ||
Comment 23•2 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D279336
Updated•2 months ago
|
Comment 24•2 months ago
|
||
firefox-release Uplift Approval Request
- User impact if declined: None, but the growth team will be unable to do experiments related to the newtab 48 hour activation window on the release channel unless this foundational code lands.
- Code covered by automated testing: yes
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: See https://gist.github.com/mikeconley/653f52f653a686c9bd8b9c83af8ec64d
- Risk associated with taking this patch: low
- Explanation of risk level: This has been on Nightly for a few days now, and is mostly just plumbing the creation date of the profile down into the newtab code, so it's fairly well understood.
- String changes made/needed: None.
- Is Android affected?: no
| Assignee | ||
Comment 25•2 months ago
|
||
This is so that if there are any other feeds that want to emit actions on initialization
that the StartupCacheInit feed should hear about, it will be initialized and be able
to hear about them.
This is needed for the PrefsFeed activation window check, which might emit actions on
initialization that a cached page should hear about.
Original Revision: https://phabricator.services.mozilla.com/D279362
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Comment 26•2 months ago
|
||
| uplift | ||
Updated•2 months ago
|
Comment 27•2 months ago
|
||
(In reply to Pulsebot from comment #12)
Pushed by mconley@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/5edf6de1d9bd
https://hg.mozilla.org/integration/autoland/rev/dca5cc891ee4
Part 1: Block initializing ActivityStream on the newtabTrainhop Nimbus
feature being ready. r=nbarrett,home-newtab-reviewers
https://github.com/mozilla-firefox/firefox/commit/c6c2729d07d3
https://hg.mozilla.org/integration/autoland/rev/8367a0687d59
Part 2: Compute instant of profile creation and have ActivityStream cache
it. r=home-newtab-reviewers,nbarrett,perftest-reviewers,kshampur
https://github.com/mozilla-firefox/firefox/commit/5791aaacec84
https://hg.mozilla.org/integration/autoland/rev/d5e09e55847e
Part 3: Make StartupCacheInit feed start first amongst feeds.
r=thecount,home-newtab-reviewers,nbarrett
Perfherder has detected a talos performance change from push d5e09e55847ecc8323f0918c6f2500149f785078.
No action is required from the author; this comment is provided for informational purposes only.
| Improvement | Test | Platform | Options | Absolute values [old vs new] |
|---|---|---|---|---|
| 2% | startup_about_home_paint_cached (doc) | linux1804-64-shippable-qr | e10s fission stylo webrender-sw | 1,032.71 -> 1,009.50 |
Need Help or Information?
If you have any questions, please reach out to afinder@mozilla.com. Alternatively, you can find help on Slack by joining #perf-help, and on Matrix you can find help by joining #perftest.
Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.
Comment 28•1 month ago
|
||
I can confirm that the Topsites and Story cards behaviour (including prefs values) matches the one described here (Steps 16-26).
- Tested versions:
- Firefox Release 147.0.3 (Build ID: 20260203002554)
- Used the builds and steps provided here
- Firefox Devedition 148.0b15 (Build ID: 20260213095341)
- Firefox Nightly 149.0a1 (BuildID: 20260220092058)
- Firefox Release 147.0.3 (Build ID: 20260203002554)
- Tested platforms:
- Windows 10 x64
- Windows 11
- macOS 15.6.1
- Linux Mint 22.2
Based on this, I am marking this issue as Verified - Fixed.
Updated•1 month ago
|
Description
•