Added a new card for the Juno Onboarding, "Add search widget
to homescreen". This is an experiment that aims to increase
DAU and searches.
(cherry picked from commit cba23f261cb6b81b60f994022ae41967e7915ade)
This bug adds telemetry for the print from menu feature. It adds the
probes print_failure, print_completed, print_tapped (for both share and
browsr menu), and share_menu_action for the print button on the share
sheet only. browser_menu_action for the print button was added in bug
1836780.
Additionally, Nimbus control for the browser print button and
share print button was added as browser-print-enabled and
share-print-enabled.
This bug adds a print button on the main Fenix toolbar menu and a print
button on the share menu.
This bug adds a main toolbar extra telemetry of
print_content. Additional telemetry and Nimbus instrumentation will be
added in bug 1837517.
* Adds `checkForPdfViewer` to determine if page is a PDF Viewer page or not
* Adjusts save_to_pdf_failure to have extras of pdf, non-pdf, or unknown
* Adjusts save_to_pdf_failure to have extras of failure reason
* Adjusts save_to_pdf_tapped to have extras of pdf, non-pdf, or unknown
* Adds save_to_pdf_completed with extras of pdf, non-pdf, or unknown
* Bug 1820211 - Adds `tabKilled` event to track when a tab was killed with form data.
- Also includes if the tab was the active tab and whether the app was in the foreground.
* Bug 1820211 - Adds tests for TelemetryMiddleware and StoreLifecycleObserver
* Bug 1820211 - Renames CheckFormDataAction to UpdateHasFormData
- Removes @property hasFormData comment from sessionState
- Moves checking formdata from TabContentMiddleware to SessionPrioritizationMiddleware
---------
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
There is a race condition with generated hashed Ad IDs because we were
using a single metric rather than separate metrics for each. We use this
new metric so we can send a differently salted version of the ad ID in
two separate pings.
* Bug 1817245 - new Nimbus feature for controlling client-deduplication ping
This feature will enable/disable the sending of the `client-deduplication`
ping that will be added in a later PR.
* Bug 1817029 - Add the client-deduplication ping
The `client-deduplication` ping will be used to determine if
client IDs are being regenerated erroneously. This ping uses
the lifecycle observers to (almost) replicate the same scheduling
as the baseline ping.
* Bug 1817029 - Suggested changes
changelog
- add `reason` for new ping
- update the unit test for the new ping
- add new metrics
- allow for custom salt when hashing the Ad ID
- move the Nimbus check to the lifecycle observer
- record the new metrics
* Bug 1817029 - Update fenix/.experimenter.yaml
Co-authored-by: Alessio Placitelli <alessio.placitelli@gmail.com>
* Bug 1817029 - remove unnecessary pass-through function
* Bug 1817029 - add the GleanTestRule for tests
* Bug 1817029 - Update fenix/app/src/test/java/org/mozilla/fenix/components/metrics/clientdeduplication/ClientDeduplicationPingTest.kt
Co-authored-by: Travis Long <tlong@mozilla.com>
* Bug 1817029 - remove unnecessary call to main thread
* Bug 1817029 - update comment about hashing
---------
Co-authored-by: Alessio Placitelli <alessio.placitelli@gmail.com>
Co-authored-by: Travis Long <tlong@mozilla.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
DreVla
Zac McKenney
Roger Yang
Gabriel Luong
t-p-white
Harrison Oglesby
Olivia Hall
mike a
Bruno Rosa
James Hugman
iorgamgabriel
Raphael Pierzina
rahulsainani
Jeff Boek
Titouan Thibaud
Alexandru2909
Mugurell
jhugman