Closed Bug 1979133 Opened 10 months ago Closed 7 months ago

Expose a pref and a Nimbus pref/variable for new link handling behavior

Categories

(Firefox :: Tabbed Browser, task, P2)

task
Points:
1

Tracking

()

RESOLVED FIXED
146 Branch
Tracking Status
firefox145 --- fixed
firefox146 --- fixed

People

(Reporter: asafko, Assigned: sthompson)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

To do a controlled introduction of the new link handling behavior, we need:

  • a pref associated with it,
  • have this pref exposed to Nimbus via Feature Manifest.

Rationale: We want to introduce new external link handling behavior in the following way:

  • Offer the setting for everyone as an opt-in (off by default)
  • In parallel, launch an experiment, making it ON by default for new users,
  • In case of no negative impact is detect, make new link handling behavior a new default for new users.

We would still need to figure out how to offer/switch existing users to this behavior (messaging, else).

Whiteboard: [fidefe-sidebar]
Blocks: 1979137
Priority: -- → P2
No longer blocks: 1979132
Component: Sidebar → Tabbed Browser
Points: --- → 1
Whiteboard: [fidefe-sidebar]

Direct pref access to browser.link.open_newwindow.override.external is replaced by a Nimbus variable openBehavior in a new Nimbus feature, externalLinkHandling. The Nimbus variable falls back to the pref value.

I also enabled the Glean metric tab_movement and event open_from_external_app. I had them start disabled because I believed that Glean's Server Knobs could turn on the telemetry just for people enrolled in the experiment. It doesn't seem like that's true, so it's easier right now to just have these pieces of telemetry enabled for everyone. These telemetry need to be in place to measure the results of the Nimbus experiment, so I included these changes in this patch.

Assignee: nobody → sthompson
Status: NEW → ASSIGNED
Pushed by sthompson@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/9a9da20b36d2 https://hg.mozilla.org/integration/autoland/rev/0c43190b74fb integrate Nimbus for experimenting with opening external links after the active tab r=jswinarton,tabbrowser-reviewers,Gijs
Status: ASSIGNED → RESOLVED
Closed: 7 months ago
Resolution: --- → FIXED
Target Milestone: --- → 146 Branch

firefox-beta Uplift Approval Request

  • User impact if declined: Low. If this patch is declined, our team will have to delay an experiment with providing the new "Open links from apps next to the active tab" optional feature as a default for new users.
  • Code covered by automated testing: yes
  • Fix verified in Nightly: yes
  • Needs manual QE test: no
  • Steps to reproduce for manual QE testing:
  • Risk associated with taking this patch: low
  • Explanation of risk level: Replaces a pref lookup with a Nimbus API call for a variable that is backed by the same pref. Fallback behavior has automated test coverage.
  • String changes made/needed: No
  • Is Android affected?: no
Attachment #9522397 - Flags: approval-mozilla-beta?

Direct pref access to browser.link.open_newwindow.override.external is replaced by a Nimbus variable openBehavior in a new Nimbus feature, externalLinkHandling. The Nimbus variable falls back to the pref value.

I also enabled the Glean metric tab_movement and event open_from_external_app. I had them start disabled because I believed that Glean's Server Knobs could turn on the telemetry just for people enrolled in the experiment. It doesn't seem like that's true, so it's easier right now to just have these pieces of telemetry enabled for everyone. These telemetry need to be in place to measure the results of the Nimbus experiment, so I included these changes in this patch.

Original Revision: https://phabricator.services.mozilla.com/D269130

Attachment #9522397 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: