Commit Graph

255 Commits (cad0e110dd4677355f3708ef52e38f36bc1b4595)

Author SHA1 Message Date
Grisha Kruglov 6a8d0f324e Closes #2770: Allow receiving tabs from FxA devices (#2772)
* Closes #2770: Allow receiving tabs from FxA devices

Now that we're on a-c 0.54, we can land this since it supports device
capability migration.

This patch adds a SEND_TAB device capability, making Fenix a valid target
in the Send Tab device list on Desktop Firefox.

Additionally, it adds a notification manager which manages notification
channels and knows how to display "received tabs" notifications".

* Post: remove unusued test file that's causing issues
5 years ago
Tiger Oakes cfca683a14 Use UpdateTrackingProtectionUseCase
mozilla-mobile/android-components#2746
5 years ago
Sawyer Blatz 72d29c2a43
For #2205 & #1578: Integrates tab collection storage (#2478)
* For #2205: Adds TabCollectionStorage

* For #1578: Adds delete to TabCollection
5 years ago
Colin Lee 96b68948b5
For #1710: Create scaffolding for Robolectric tests (#2282) 5 years ago
Alessio Placitelli 0d82431195 Generate the `activation` ping and send it with Glean (#1707)
This fetches the Google Advertising ID, salts it and
then applies hashing before sending a ping with it,
at startup. Hashing and salting are used in order
to prevent ourselves to correlate advertising IDs
from the same user running different products we
own off a single device. We will never send the
client_id and the Google Advertising ID in the same
ping.
5 years ago