[MCAB HNT] Phase 6: Enable new tab search bar in Nightly
Categories
(Firefox :: Address Bar, task, P2)
Tracking
()
People
(Reporter: dao, Assigned: dao)
References
(Blocks 1 open bug, Regressed 1 open bug)
Details
(Keywords: perf-alert, Whiteboard: [sng][mcab-hnt])
Attachments
(2 files, 1 obsolete file)
Part of the MCAB HNT roadmap: putting <moz-urlbar> on the Home / New Tab page.
Roll out the newtab <moz-urlbar> through browser.urlbar.newtab.featureGate in two stages: a build-time default flip for Nightly, then a remote Nimbus recipe for the ramp to release. Blocked on the end-to-end tests being green and the styling being correct.
a. Nightly-on by default. Replace the flat false default in firefox.js with an #ifdef NIGHTLY_BUILD override, keeping the PREF_URLBAR_DEFAULTS map entry false as the release fallback (the browser.urlbar.autoFill.adaptiveHistory.enabled precedent). Done when Nightly shows the newtab <moz-urlbar> by default and release/beta still show the handoff bar.
b. Wire the gate to Nimbus. Add a variable under the urlbar feature in toolkit/components/nimbus/FeatureManifest.yaml with fallbackPref: browser.urlbar.newtab.featureGate, following the *.featureGate fallbackPref pattern already used there. UrlbarPrefs resolves the Nimbus value over the pref default, so no read-side wiring is needed. Confirm the variable name doesn't collide with an existing urlbar feature variable.
c. Author the Nimbus rollout recipe. With the gate remotely controllable, author a rollout in Experimenter targeting release users -- a staged percentage ramp, reversible by disabling the rollout. The build-time #ifdef stays Nightly-only so release safety doesn't depend on the recipe staying live.
Updated•29 days ago
|
| Assignee | ||
Updated•29 days ago
|
Updated•29 days ago
|
| Assignee | ||
Comment 1•15 days ago
|
||
Not ready to land: the end-to-end tests and the styling have to be there first. The PREF_URLBAR_DEFAULTS entry stays false, so a build without the pref still reads the gate as off.
| Assignee | ||
Comment 2•15 days ago
|
||
The next commit makes the gate default on for Nightly, which supersedes the handoff bar and leaves these tests waiting for markup that is no longer there.
| Assignee | ||
Comment 3•14 days ago
|
||
The pref becomes the variable's fallback, so both registrants read newtabFeatureGate instead: a raw pref read does not see an enrollment.
Updated•14 days ago
|
Updated•14 days ago
|
Updated•14 days ago
|
Comment 4•13 days ago
|
||
Comment on attachment 9630479 [details]
Bug 2062212 - Put the newtab feature gate under Nimbus control. r?daleharvey!
Revision D321164 was moved to bug 2066752. Setting attachment 9630479 [details] to obsolete.
| Assignee | ||
Updated•13 days ago
|
| Assignee | ||
Updated•13 days ago
|
Updated•13 days ago
|
Comment 7•13 days ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/540bd3cda62f
https://hg.mozilla.org/mozilla-central/rev/70ae344e0fd3
Updated•12 days ago
|
| Assignee | ||
Comment 8•12 days ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]:
[Affects Firefox for Android]:
[Suggested wording]: The search bar on the new tab is a real search bar now, showing results on the page instead of sending you to the address bar.
[Links (documentation, blog post, etc)]:
Comment 9•12 days ago
|
||
Added to the Fx156 nightly release notes, please allow 30 minutes for the site to update.
The nightly-only note will be removed after three cycles or when it is enabled by default, whichever comes earlier.
Comment 10•5 days ago
|
||
Perfherder has detected a talos performance change from push 70ae344e0fd37807d3806e937d9ea8490045fbbf.
No action is required from the author; this comment is provided for informational purposes only.
| Improvement | Test | Platform | Options | Absolute values [old vs new] |
|---|---|---|---|---|
| 7% | tart (doc) | linux2404-64-shippable | e10s fission stylo webrender-sw | 2.64 -> 2.45 |
| 7% | tart (doc) | linux2404-64-shippable | e10s fission stylo webrender | 2.41 -> 2.24 |
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.
Description
•